| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 18 Feb 2007 21:13:03 -0800 From: David Brownell <david-b@...bell.net> To: Andrew Morton <akpm@...ux-foundation.org> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org Subject: Re: 2.6.20-mm2 On Sunday 18 February 2007 4:28 pm, Andrew Morton wrote: > On Mon, 19 Feb 2007 00:32:08 +0100 "Rafael J. Wysocki" <rjw@...k.pl> wrote: > > > One more thing: > > > > rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0 > > Unable to handle kernel NULL pointer dereference at 0000000000000030 RIP: > > [<ffffffff804032c3>] rtc_sysfs_remove_device+0x23/0x50 > > ... > > Call Trace: > > [<ffffffff803c5786>] class_device_del+0x86/0x180 > > [<ffffffff803c5891>] class_device_unregister+0x11/0x20 > > [<ffffffff8040280e>] rtc_device_unregister+0x3e/0x50 > > [<ffffffff880cd789>] :rtc_cmos:cmos_pnp_probe+0x219/0x240 > > [<ffffffff803988a1>] pnp_device_probe+0xa1/0xe0 > > ... > > How did you provoke that? modprobe rtc-cmos? Plus, I'd guess, the old rtc driver statically linked. What I see is a should-not-happen fault of some kind in a cleanup path that's been tested with non-PNP rtc drivers. A quick glance at the code left me puzzled. Would sleeping a second or two before calling rtc_device_unregister() change that behavior? - Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists