linux-kernel - PROBLEM: Kernel Oops when unplugging USB

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-next>] [day] [month] [year] [list]

Date:	Mon, 19 Mar 2012 15:51:43 +0100
From:	Mate Soos <mate@...abs.de>
To:	<linux-kernel@...r.kernel.org>
Subject: PROBLEM: Kernel Oops when unplugging USB

Hi,

I had a kernel oops, so I thought I might report it.

[1.] One line summary of the problem
See 'messages' for the actual kernel oops messages.

[2.] Full description of the problem/report:
The kernel oops-ed when I pulled out an umounted 8GB USB key. This seems
to be visible in the "messages" file. All the data attached, except for
the "messages" has been produced after a reboot, since the system
hanged. Luckily, the "messages" got saved. The system after restart
should have exactly the same modules loaded as before.

[3.] Keywords (i.e., modules, networking, kernel):
USB, Kernel Ooops, Watchdog

[4.] Kernel version (from /proc/version):
$ cat
 /proc/version
Linux version 3.2.0-1-amd64 (Debian 3.2.4-1) (waldi@...ian.org) (gcc
version 4.6.2 (Debian 4.6.2-12) ) #1 SMP Sun Feb 5 15:17:15 UTC 2012

It's from Debian squeeze, debian package version "linux-image-3.2.0-1-amd64"

[5.] Output of Oops.. message (if applicable) with symbolic information
     resolved (see Documentation/oops-tracing.txt)
In the "messages" text file you will find these.

[6.] A small shell script or example program which triggers the
     problem (if possible)
Unfortunately, I can't reproduce.

[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
Attached.

[7.2.] Processor information (from /proc/cpuinfo):
Attached.

[7.3.] Module information (from /proc/modules):
Attached.

[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
Both attached.

[7.5.] PCI information ('lspci -vvv' as root)
Attached.

[7.6.] SCSI information (from /proc/scsi/scsi)
bash: /proc/scsi/scsi: No such file or directory

I hope this helps in triaging and/or resolving this bug!

Thanks,

Mate

-- 
Mate Soos
Security Research Labs
http://www.srlabs.de

View attachment "cpuinfo" of type "text/plain" (6680 bytes)

View attachment "modules" of type "text/plain" (6330 bytes)

View attachment "ioports" of type "text/plain" (1779 bytes)

View attachment "iomem" of type "text/plain" (2300 bytes)

View attachment "lspci" of type "text/plain" (56810 bytes)

View attachment "messages" of type "text/plain" (98822 bytes)

View attachment "ver_linux" of type "text/plain" (1933 bytes)

Download attachment "smime.p7s" of type "application/pkcs7-signature" (6252 bytes)