Re: [PATCH] list module taint flags in Oops/panic

[Alistair John Strachan <s0348365@sms.ed.ac.uk>]

On Friday 29 September 2006 03:12, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> When listing loaded modules during an oops or panic, also list each
> module's Tainted flags if non-zero (P: Proprietary or F: Forced load only).
>
> If a module is did not taint the kernel, it is just listed like
> 	usbcore
> but if it did taint the kernel, it is listed like
> 	wizmodem(PF)
>
> Example:
> [ 3260.121718] Unable to handle kernel NULL pointer dereference at
> 0000000000000000 RIP: [ 3260.121729]  [<ffffffff8804c099>]
> :dump_test:proc_dump_test+0x99/0xc8 [ 3260.121742] PGD fe8d067 PUD 264a6067
> PMD 0
> [ 3260.121748] Oops: 0002 [1] SMP
> [ 3260.121753] CPU 1
> [ 3260.121756] Modules linked in: dump_test(P) snd_pcm_oss snd_mixer_oss
> snd_seq snd_seq_device ide_cd generic ohci1394 snd_hda_intel snd_hda_codec
> snd_pcm snd_timer snd ieee1394 snd_page_alloc piix ide_core arcmsr aic79xx
> scsi_transport_spi usblp [ 3260.121785] Pid: 5556, comm: bash Tainted: P   
>   2.6.18-git10 #1
>
> [Alternatively, I can look into listing tainted flags with 'lsmod',
> but that won't help in oopsen/panics so much.]

I think this is definitely a good start.

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.