So, 5.14.7 and NVIDIA 470.74 fixes the boot issue. However, isn't potentially harmful to leave CONFIG_UBSAN_TRAP enabled in production builds? The documentation for the flag seems to indicate that warnings would be turned into the errors.
https://github.com/torvalds/linux/blob/master/lib/Kconfig.ubsan#L20 As I understand, CONFIG_UBSAN_TRAP is needed to enable CONFIG_UBSAN_LOCAL_BOUNDS, but the issue mentions CONFIG_UBSAN_BOUNDS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1914685 Title: Please enable CONFIG_UBSAN_BOUNDS Status in linux package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Committed Status in linux source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux source package in Hirsute: Confirmed Status in linux-oracle source package in Hirsute: Confirmed Status in linux source package in Impish: Fix Released Status in linux-oracle source package in Impish: Fix Committed Bug description: Enabling CONFIG_UBSAN_BOUNDS is fast and provides good coverage for out-of-bounds array indexing (i.e. it catchings the things that CONFIG_FORTIFY doesn't). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
