summaryrefslogtreecommitdiffstats
path: root/fs/bio.c
diff options
context:
space:
mode:
authorArjan van de Ven <arjan@linux.intel.com>2008-01-25 21:08:33 +0100
committerIngo Molnar <mingo@elte.hu>2008-01-25 21:08:33 +0100
commite14af7eeb47ea96c52741c5e5fa010d33daf6973 (patch)
tree0b4c1af86e766726ba75873812715706e4044086 /fs/bio.c
parent21aa9280b9f4e9e68d3fa8990df6c9d7fd71f994 (diff)
downloadop-kernel-dev-e14af7eeb47ea96c52741c5e5fa010d33daf6973.zip
op-kernel-dev-e14af7eeb47ea96c52741c5e5fa010d33daf6973.tar.gz
debug: track and print last unloaded module in the oops trace
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. [ mingo@elte.hu: build fix ] Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'fs/bio.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud