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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 21 Feb 2007 19:57:00 -0800
From:	David Brownell <david-b@...bell.net>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-mm2

On Tuesday 20 February 2007 2:07 pm, Rafael J. Wysocki wrote:

> > Plus, I'd guess, the old rtc driver statically linked.
> 
> Yes (mistakenly).

Until someone merges the BSOD-for-Linux patch, I'll continue to
assume that oopsing is the wrong response to "user" mistakes.  ;)

Legacy drivers can be such a PITA.


> > 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?
> 
> [tries]
> 
> No.

Shoot.  OK, I'll see if I can reproduce it myself.  Is this system
using a generic CMOS RTC?  Or is HPET somehow involved?  (That old
RTC driver has HPET voodoo as well as normal RTC stuff.)

- 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/