Bug 31802 - usb mass storage error causes kernel panic
Summary: usb mass storage error causes kernel panic
Status: RESOLVED CODE_FIX
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Block Layer (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jonathan Nieder
URL: http://bugs.debian.org/cgi-bin/bugrep...
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-24 11:44 UTC by Michal Suchanek
Modified: 2012-05-19 16:27 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.38
Subsystem:
Regression: No
Bisected commit-id:

Attachments
screenshot of the kernel panic (503.39 KB, image/jpeg)
2011-03-24 11:44 UTC, Michal Suchanek 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Michal Suchanek 2011-03-24 11:44:57 UTC 
Created attachment 51872 [details]
screenshot of the kernel panic

To reproduce:

1) Attach a SATA drive to a SATA/USB bridge.
2) dd if=/dev/urandom of=/dev/sdf bs=4k
3) detach the drive drom the bridge


Bus 002 Device 003: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Comment 1 Eugeni Dodonov 2011-04-18 18:31:08 UTC 
I can reproduce it with 2.6.38.3 too.
Comment 2 Alan 2012-05-12 14:52:27 UTC 
Should be fixed as of 3.0
Comment 3 Jonathan Nieder 2012-05-14 21:09:09 UTC 
Fixed by v3.1-rc1~241^2~121 (ipc/sem.c: fix race with concurrent semtimedop() timeouts and IPC_RMID, 2011-07-25)?
Comment 4 Ben Hutchings 2012-05-19 16:20:28 UTC 
(In reply to comment #3)
> Fixed by v3.1-rc1~241^2~121 (ipc/sem.c: fix race with concurrent semtimedop()
> timeouts and IPC_RMID, 2011-07-25)?

I don't think so!  I think this one was finally fixed by:

commit 777eb1bf15b8532c396821774bf6451e563438f5
Author: Hannes Reinecke <hare@suse.de>
Date:   Wed Sep 28 08:07:01 2011 -0600

    block: Free queue resources at blk_release_queue()

included in 3.1 and 3.0.5.
Comment 5 Jonathan Nieder 2012-05-19 16:27:59 UTC 
Thanks, that one makes more sense.  Closing again, but confirmation either
way about the fix (from testing any newish kernel) would be welcome.
Note You need to log in before you can comment on or make changes to this bug.