linux-kernel - Re: [BUG] Oops in USB / dev code plugging/unplugging multi flash reader

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: <20071128232415.GA11926@suse.de>
Date:	Wed, 28 Nov 2007 15:24:15 -0800
From:	Greg KH <gregkh@...e.de>
To:	Mark Lord <lkml@....ca>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] Oops in USB / dev code plugging/unplugging multi flash
	reader

On Wed, Nov 28, 2007 at 06:17:39PM -0500, Mark Lord wrote:
> Greg KH wrote:
>> On Wed, Nov 28, 2007 at 03:02:35PM -0500, Mark Lord wrote:
>>> While testing a new USB reader/cable today,
>>> I was plugging/unplugging the USB multi-flash reader (22 in 1),
>>> and produced this weird oops.
>>>
>>> There's a locking problem in there somewhere, Greg.
>>>
>>> 2.6.23.8
>> Can you duplicate this without the closed source ATI graphics driver 
>> loaded?
> ..
>
> I don't know if I can reproduce it easily regardless.
> But that fglrx module has ZERO users, so it was completely benign here
> (I've now deleted it from my system).
>
> The tracebacks clearly show USB/dev error.

I'm not disagreeing, but I've seen some very strange crap over the years
come from those closed source video drivers so I do not trust them at
all.

If you can reproduce this without it loaded, please send the new oops
message to the linux-usb mailing list and the developers there will be
glad to work with you to track this down.

Oh, can you also reproduce it with 2.6.24-rc3?

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/