linux-kernel - Re: intensive IO on usb-storage device causing system lock

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]

Date:	Wed, 11 Feb 2015 10:21:50 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Enrico Mioso <mrkiko.rs@...il.com>
cc:	linux-usb@...r.kernel.org, <linux-kernel@...r.kernel.org>
Subject: Re: intensive IO on usb-storage device causing system lock

On Tue, 10 Feb 2015, Enrico Mioso wrote:

> Hello guys.
> the problem is still reproducible with final 3.19 kernel - I can confirm it.
> Re-sending the last trace here - don't know if it's available in cxg.de.

Please stop posting these process traces.  They don't help.

Instead, post a usbmon trace showing what happens around the time when 
the problem occurs.  If the trace file is quite large (which is likely, 
because usbmon can generate a lot of data in a short time), you can 
cut out everything up to the last few hundreds of KB before the problem 
starts.

> For those who might not have read the thread - the problem is: after some
> intensive IO to an USB (usb-storage) disk, for a more or less long time,
> depending on the quantity of IO you do, there start to be situations where some
> processes get stuck doing IO, in any case. Not IO to the USB disk, but IO also 
> to other devices, like the one where the root partition resides, in my case a 
> flash drive. I am using an EEE PC 701.

That sounds like the problem may lie somewhere other than in the USB 
stack.  But there's no way to tell without seeing a usbmon trace.

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/