linux-kernel - Re: Lockup on USB and block devices

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:   Mon, 14 Oct 2019 13:59:41 +0200
From:   Oliver Neukum <oneukum@...e.com>
To:     Alan Stern <stern@...land.harvard.edu>,
        Steven Rostedt <rostedt@...dmis.org>
Cc:     Jens Axboe <axboe@...nel.dk>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-block@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        linux-usb@...r.kernel.org
Subject: Re: Lockup on USB and block devices

Am Dienstag, den 01.10.2019, 14:31 -0400 schrieb Alan Stern:
> It looks like a problem with your xHCI USB host controller.  Normally a
> usb-storage transfer would be aborted after 90 seconds.  But if the
> host controller (or its driver) isn't working right, and the abort
> never completes, you end up with a situation like this -- usb-storage
> and the higher SCSI and block layers waiting indefinitely for an event
> that won't occur.

Hi,

that would imply that usb_unlink_urb() is malfunctioning
without taking down the whole bus. Is that likely?

	Regards
		Oliver