On Wed, 2013-08-07 at 19:37 +0200, Borislav Petkov wrote: > On Wed, Aug 07, 2013 at 01:33:06PM -0400, Steven Rostedt wrote: > > Right, and this code keeps the same logic as it was before. If it was > > disabled by CONFIG_EXPERT, it stays disabled, but at least you get to > > see a warning that your kernel may be corrupt now :-) > > Don't we really want to panic instead of running a corrupt kernel? IOW, > to change the logic to panic unconditionally because the image in memory > has been violated and not in a good way, at that :-)
Well, there's lots of places that use BUG() for a corrupt kernel. If you are stupid enough to disable it, you get what you asked for. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
