Alright, I checked with Chris Chiu, he confirms that all the tests kernels that he provided don't have -fcf-protection=none. However, we still don't think that touching this compiler option is a proper fix for the bug, more likely it's just hiding the problem, so we could still have a potential stack corruption somewhere.
If possible I would like to test a kernel with KASAN enabled to see if we can get additional information about the stack corruption. I've prepared another test kernel (latest 5.13.0-22-generic w/ KASAN enabled): https://kernel.ubuntu.com/~arighi/lp1945590/ If anybody could test this and share the kernel oops/panic info here it'd be great! And hopefully this will help us to understand exactly where and how the stack corruption happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
