Messages in this thread | | | Subject | Re: preempt with selinux NULL pointer dereference | From | Antoine Martin <> | Date | Fri, 05 Aug 2005 17:46:13 +0100 |
| |
> > [ 4788.218951] Unable to handle kernel NULL pointer dereference at 0000000000000028 RIP: > > [ 4788.218959] <ffffffff80247381>{inode_has_perm+81} > > [ 4788.218971] PGD 2485f067 PUD 0 > > [ 4788.218975] Oops: 0000 [1] PREEMPT > > [ 4788.218977] CPU 0 > > [ 4788.218979] Modules linked in: parport_pc lp parport eeprom i2c_sensor i2c_viapro i2c_dev i2c_core rfcomm l2cap bluetooth sunrpc ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables dm_mod hotkey container tsdev usbhid yenta_socket rsrc_nonstatic uhci_hcd ehci_hcd shpchp via_ircc irda crc_ccitt > > [ 4788.218995] Pid: 19002, comm: ssh Tainted: G M 2.6.13-rc5 > > Which of your modules is non-GPL and can you please remove them and see if > there's still a problem? Hmm. I occasionally use out-of-tree drivers (wlan cards mainly) so I thought these could be the culprit, but all the above are in the source tree (I keep the others out): lsmod | awk '{print $1".ko"}' | sed 's+_+-+g' | xargs -n 1 find /lib/modules/2.6.13-rc5 -type f -name /lib/modules/2.6.13-rc5/kernel/drivers/char/lp.ko /lib/modules/2.6.13-rc5/kernel/drivers/parport/parport.ko /lib/modules/2.6.13-rc5/kernel/drivers/i2c/chips/eeprom.ko /lib/modules/2.6.13-rc5/kernel/drivers/i2c/i2c-sensor.ko /lib/modules/2.6.13-rc5/kernel/drivers/i2c/busses/i2c-viapro.ko /lib/modules/2.6.13-rc5/kernel/drivers/i2c/i2c-dev.ko /lib/modules/2.6.13-rc5/kernel/drivers/i2c/i2c-core.ko /lib/modules/2.6.13-rc5/kernel/net/bluetooth/rfcomm/rfcomm.ko /lib/modules/2.6.13-rc5/kernel/net/bluetooth/l2cap.ko /lib/modules/2.6.13-rc5/kernel/net/bluetooth/bluetooth.ko /lib/modules/2.6.13-rc5/kernel/net/sunrpc/sunrpc.ko /lib/modules/2.6.13-rc5/kernel/drivers/md/dm-mod.ko /lib/modules/2.6.13-rc5/kernel/drivers/acpi/hotkey.ko /lib/modules/2.6.13-rc5/kernel/drivers/acpi/container.ko /lib/modules/2.6.13-rc5/kernel/drivers/input/tsdev.ko /lib/modules/2.6.13-rc5/kernel/drivers/usb/input/usbhid.ko /lib/modules/2.6.13-rc5/kernel/drivers/usb/host/uhci-hcd.ko /lib/modules/2.6.13-rc5/kernel/drivers/usb/host/ehci-hcd.ko /lib/modules/2.6.13-rc5/kernel/drivers/pci/hotplug/shpchp.ko /lib/modules/2.6.13-rc5/kernel/drivers/net/irda/via-ircc.ko /lib/modules/2.6.13-rc5/kernel/net/irda/irda.ko /lib/modules/2.6.13-rc5/kernel/lib/crc-ccitt.ko (iptables ones omitted)
Is there an *easy* way to figure out what is tainting my kernel? I removed all I could (whilst leaving the machine usable): # lsmod Module Size Used by tsdev 8832 0 usbhid 48992 0 uhci_hcd 36000 0 parport_pc 44080 0 parport 42444 1 parport_pc i2c_sensor 3840 0 i2c_core 25048 1 i2c_sensor l2cap 29704 2 bluetooth 56516 3 l2cap sunrpc 163688 1 ipt_REJECT 6464 1 ipt_state 2368 3 ip_conntrack 49812 1 ipt_state iptable_filter 3584 1 ip_tables 24000 3 ipt_REJECT,ipt_state,iptable_filter yenta_socket 25804 4 rsrc_nonstatic 13376 1 yenta_socket irda 210924 0 crc_ccitt 2560 1 irda
# cat /proc/sys/kernel/tainted 16 Even figuring out the definition of the 'tainted' masks took a bit of googling.
Thanks Antoine
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |