It'd be helpful if this memory corruption regression could be accelerated. It means that unplugging a USB3 device can mess up the memory enough that file lookups that happen afterwards break if apparmor is enabled - just because the allocation size is similar by chance. The resulting oops is very misleading and it took a long time to track this down. It also causes process hangs. Thanks.
It'd be helpful if this memory corruption regression could be accelerated. It means that unplugging a USB3 device can mess up the memory enough that file lookups that happen afterwards break if apparmor is enabled - just because the allocation size is similar by chance. The resulting oops is very misleading and it took a long time to track this down. It also causes process hangs. Thanks.