netdev - Re: Oops/Warning report for the week of March 28th 2008

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]

Message-ID: <Pine.LNX.4.64.0803282309040.32241@twin.jikos.cz>
Date:	Fri, 28 Mar 2008 23:14:58 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Johannes Berg <johannes@...solutions.net>
cc:	Arjan van de Ven <arjan@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	NetDev <netdev@...r.kernel.org>, Dmitry Torokhov <dtor@...l.ru>
Subject: Re: Oops/Warning report for the week of March 28th 2008

On Fri, 28 Mar 2008, Linus Torvalds wrote:

> > I tend to think it's actually a regression, I've done exactly what I 
> > described there dozens of times before on older kernels and it doesn't 
> > seem to be a race condition, X always locks the input device and I 
> > never had trouble with that before.
> Ahh. So it's easily repeatable for you.. Do you think you could bisect it? 
> At least a few runs? Even a partial bisection will give a nice (== much 
> smaller) range of commits to be blamed, and might tell us why it started 
> happening..

... and if bisecting the whole tree isn't the way for you to go right now, 
maybe restricting to drivers/input/ and drivers/base/ (as I think this 
might be some broken driver core refcounting) and possibly drivers/hid/ 
(if you are using any HID input device) might also be sufficient.

-- 
Jiri Kosina
SUSE Labs

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html