linux-kernel - Re: [PATCH] USB: fix interrupt disabling for HCDs with shared interrupt handlers

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

Date:	Tue, 1 Jul 2008 12:51:19 -0700
From:	Greg KH <greg@...ah.com>
To:	Stefan Becker <Stefan.Becker@...ia.com>
Cc:	ext Greg KH <gregkh@...e.de>, linux-usb@...r.kernel.org,
	ext Alan Stern <stern@...land.harvard.edu>,
	ext David Brownell <david-b@...bell.net>,
	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	ext Leonardo Chiquitto <leonardo.lists@...il.com>
Subject: Re: [PATCH] USB: fix interrupt disabling for HCDs with shared
	interrupt handlers

On Tue, Jul 01, 2008 at 10:15:08PM +0300, Stefan Becker wrote:
> Hi,
>
> ext Greg KH wrote:
>> Hm, isn't this also an issue in 2.6.25 as well?  I've had a few very
>> strange reports of USB just locking up in 2.6.25, could this also be the
>> cause there?
>
> As I wrote in the first mail of this thread the problem was uncovered on my 
> machine by the following commit from 2.6.24-development:
>
> commit e9df41c5c5899259541dc928872cad4d07b82076
> USB: make HCDs responsible for managing endpoint queues
>
> The interrupt problem exists also in 2.6.23 (and previous) but the USB code 
> was not affected, as the old versions of the functions were using 
> spin_lock_irqsave().
>
> I just applied my patch to 2.6.24 & 2.6.25: it applies fine and compiles 
> without problem. So it could be submitted to the 2.6.24.X and 2.6.25.X 
> branches too.

Thanks, I'll queue it up for there as well.

greg k-h
--
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/