Comment 9 for bug 1914685

Revision history for this message
Rashad Tatum (rmtatum) wrote (last edit ):

So, 5.14.7 and NVIDIA 470.74 fixes the boot issue. However, isn't it 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.