linux-kernel - Re: 2.6.20-mm2

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200703042336.09103.rjw@sisk.pl>
Date:	Sun, 4 Mar 2007 23:36:08 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	David Brownell <david-b@...bell.net>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-mm2

On Friday, 23 February 2007 17:36, David Brownell wrote:
> > > > > 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
> 
> The bug isn't in rtc_cmos, but that's the only driver that would currently
> show the bug.  (Triggered by finding the IRQ claimed by the legacy driver,
> result of a "but it should still be safe!" misconfiguration.)
> 
> The following fixes this on my 2.6.21-rc1 system; same fix should apply
> to MM2.
> 
> =====================	CUT HERE
> Fix an oops on the rtc_device_unregister() path by waiting until the
> last moment before nulling the rtc->ops vector.  Fix some potential
> oopses by having the rtc_class_open()/rtc_class_close() interface
> increase the RTC's reference count while an RTC handle is available
> outside the RTC framework.
> 
> Signed-off-by: David Brownell <dbrownell@...rs.sourceforge.net>

The patch fixes the Oops on my Asus L5D and allows it to suspend to disk
(without it the problem is present in 2.6.21-rc1 and 2.6.21-rc2).

I think it should go into 2.6.21.

Greetings,
Rafael
-
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/