linux-kernel - Re: [linux-usb-devel] 2.6.23-rc3 USB segfaults + urb status -32

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: <Pine.LNX.4.44L0.0709081802500.26094-100000@netrider.rowland.org>
Date:	Sat, 8 Sep 2007 18:15:25 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Lasse Kärkkäinen <tronic+1kf5@....iki.fi>
cc:	linux-kernel@...r.kernel.org,
	<linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.23-rc3 USB segfaults + urb status -32

On Sun, 9 Sep 2007, Lasse Kärkkäinen wrote:

> Sorry about late reply. I have been extremely busy with other things.
> 
> > Does 2.6.22 work fine?
> 
> Not perfect, but it does not crash spontaneously. I have been running
> 2.6.22-ck1 since my last email with only one crash and today I have
> tortured 2.6.22.5 as badly as I can (switching bConfigurationValue of
> the sound card, unplugging USB devices on fly, doing heavy I/O, etc),
> without crashes.
> 
> However, with 2.6.23-rc5 I still got segfaults on boot¹ (log1),

Those were problems with the usb_id program, not problems in the 
kernel.  How up-to-date is your udev installation?

> a few
> dozen urb status -32 messages by powering off the sound card while it
> was in use (log2),

Nothing wrong with that.  You should expect that removing a device 
while it is use would produce a few error messages.

> but no crashes there. It did finally crash (log3),
> though, after about three hours of coding + listening to music on text
> console (no Nvidia drivers nor any other external modules). Apparently
> it reset all USB buses, including the one that my system disk is
> connected to (there is nothing else on the same port), effectively
> killing the system, even though technically it didn't crash.

There's no indication in the log that the disk problem was at all
related to the sound card.  Nor is there any indication that all your
USB buses were affected; only the disk drive got messed up.  The card
reader, the hub, the keyboard, and the mouse all seem to have survived.

> It also seems that .23-rc5 no longer exposes bConfigurationValue and a
> few other settings under /sys/bus/usb/devices/*/,

Sure it does.

> so I couldn't test if
> switching the bConfigurationValue of the sound card still causes
> crashes² there (it has been a reliable way to do that in the past).
> 
> I could not reproduce the excessive log flood of urb status -32,
> mentioned in my original message.
> 
> The logs are here:
> http://delenn.homelinux.net/kernel-usb/
> 
> ¹) I gather that usb_id is something related to udev. It does not crash
> with .22 kernels, only with the .23 series.
> ²) OOPSes, to be specific, IIRC.

The events in your logs are not oopses.  The program segfaults, which
means that the crash occurs in userspace, not while the program is
running in the kernel.

Alan Stern

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