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

Message-ID: <46E30F24.3060604@trn.iki.fi>
Date:	Sun, 09 Sep 2007 00:07:48 +0300
From:	Lasse Kärkkäinen <tronic+1kf5@....iki.fi>
To:	linux-kernel@...r.kernel.org
CC:	linux-usb-devel@...ts.sourceforge.net
Subject: Re: 2.6.23-rc3 USB segfaults + urb status -32

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), a few
dozen urb status -32 messages by powering off the sound card while it
was in use (log2), 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.

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

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