On 5/6/20 2:01 PM, Tetsuji Rai wrote:
Hi Martin,
Thank you for your reply!
Spot on!
It was my kernel config problem associated with stronger stack
protection of gcc-10, not a gcc problem. But I can't find this in
kernel.org bugzilla or bugzilla.redhat.com (searched with "gcc 10" and
"gcc-10".)
It was probably not reported to Linux bugzilla.
It happens not in qemu or any VM, but on a native machine. As in
https://bugzilla.redhat.com/show_bug.cgi?id=1796780 (this is the first
url in the page you mentioned), turning CONFIG_STACKPROTECTOR_STRONG
off, lo and behold, the kernel works perfectly!! And as a matter of
course, it works for the latest kernel 5.6.11 also.
My problem was that I brought my custom kernel config file from Fedora
31 with gcc-9. I should have started from the prototype config file
/boot/config-5.6.8-300.fc32.x86_64, where CONFIG_STACKPROTECTOR_STRONG
is off for its native gcc.
Thank you very much!!
Great it's a known issue.
Martin
-Tetsuji
On 5/6/20 4:19 PM, Martin Liška wrote:
On 5/6/20 6:44 AM, Tetsuji Rai via Gcc wrote:
I wonder how Fedora project built its own kernel. I can't build custom
kernel with it.
What's wrong with 10.1-RC or how can I report my problem?
Hi.
Is it possible that you reached
https://lore.kernel.org/lkml/20200417190607.GY2424@tucnak/T/ ?
I can try to reproduce that but please file a bug at or bugzilla and
provide
steps how to reproduce the issue. Can you also reproduce it within a
qemu VM?
Thanks,
Martin
