On Mon, May 21, 2012 at 12:59:59PM -0700, Kees Cook wrote: [...] > Hrm. This complicates testing a bit. I need more convincing. :) > > Systems run with panic_on_oops=0, and plenty of failure paths will > just kill "current" instead of bringing the entire system down. I > would much rather allow for the possibility to get oopses when they > happen than to have to wait a full reboot cycle to "notice" them. Well, as I use qemu/kvm for testing, rebooting is actually faster than waiting for 60 seconds, so I didn't consider this use-case. :-) But yes, I see the point: as pstore's debug function of itself, updates might make sense. So, you mentioning the panic_on_oops made me think of a kernel command line option, this will also eliminate the 60 seconds hard- coded interval. But personally I'd still like it disabled by default, otherwise it is possible pstore to screw things because of itself, and that eliminates the point of having it as a reliable debug facility; IMO, it should as much non-intrusive by default as possible, and that's what we would want for production kernels anyway. I'll replace this patch with another one that will add pstore.update_ms kernel command line option. Thanks! -- Anton Vorontsov Email: cbouatmailru@xxxxxxxxx _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
