linux-kernel - Re: [PATCH] base/class.c: prevent ooops due to insert/remove race

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 29 Nov 2007 08:27:27 -0800
From:	Greg KH <gregkh@...e.de>
To:	Mark Lord <lkml@....ca>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] base/class.c: prevent ooops due to insert/remove race

On Thu, Nov 29, 2007 at 10:41:29AM -0500, Mark Lord wrote:
> Greg KH wrote:
>> On Wed, Nov 28, 2007 at 11:00:36PM -0500, Mark Lord wrote:
>>> While doing insert/remove (quickly) tests on USB, I managed to trigger
>>> an Oops on 2.6.23.1 on the call to strlen() in make_class_name().
>>>
>>> This patch prevents this oops.
>>>
>>> There is still the larger problem of the overall race
>>> that caused this in the first place, but much of the rest
>>> of the code in class.c appears to also do NULL checks to
>>> avoid Oops'ing, so this continues the tradition.
>>>
>>> Signed-off-by:  Mark Lord <mlord@...ox.com>
>> As this is a bandage over the real problem, I'd prefer to not apply this
>> one right now until we find the root cause.
> ...
>
> Ahh.. but the problem there, is that you've already said you will
> not be looking for any cause.

I will not be looking for any cause _while_ you can only reproduce this
with a closed source kernel module loaded.

> This patch prevents the Oops,
> in the same manner as existing code in that same file.
>
> Would you perhaps prefer a second patch to remove all of the other
> existing bandages from that file?  I don't think so.
>
> This patch fixes a *real* ooops that can occur on servers, desktops,
> and portables whenever a USB device is connected.

You have seen this oops on all of these types of machines?  So far you
are the only one reporting it, and only on one machine, right?

Again, please reproduce this on a non-tainted machine and send the oops
to the linux-usb mailing list so that the developers there can help you
out.

thanks,

greg k-h
-
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/