On Monday 07 January 2008 10:19:46 Arjan van de Ven wrote: > Subject: track and print last unloaded module in the oops trace > From: Arjan van de Ven <[EMAIL PROTECTED]> > CC: [EMAIL PROTECTED] > CC: [EMAIL PROTECTED] > CC: [EMAIL PROTECTED] > > Based on a suggestion from Andi: > In various cases, the unload of a module may leave some bad state around > that causes a kernel crash AFTER a module is unloaded; and it's then hard > to find which module caused that. > > This patch tracks the last unloaded module, and prints this as part of the > module list in the oops trace. > > Right now, only the last 1 module is tracked; I expect that this is enough > for the vast majority of cases where this information matters; if it turns > out that tracking more is important, we can always extend it to that. > > Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
Thanks, applied. Rusty. -- 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/
