linux-kernel - Re: USB OOPS 2.6.25-rc2-git1

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]

Message-ID: <Pine.LNX.4.44L0.0802201606430.7212-100000@iolanthe.rowland.org>
Date:	Wed, 20 Feb 2008 16:16:15 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	David Brownell <david-b@...bell.net>
cc:	Andre Tomt <andre@...t.net>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>
Subject: Re: USB OOPS 2.6.25-rc2-git1

On Wed, 20 Feb 2008, Andre Tomt wrote:

> David Brownell wrote:
> > On Tuesday 19 February 2008, Andre Tomt wrote:
> >>> Can you try this diagnostic patch, to see if it reports any messages
> >>> about IAA and/or IAAD oddities?  There's surely a quick workaround
> >>> for this, but I'd rather understand the root cause before patching.
> >> Doesn't seem to have triggered anything. dmesg attached in case I missed 
> >> anything.
> > 
> > You don't seem to have enabled CONFIG_USB_DEBUG, as the patch instructions
> > say is needed to get such diagnostics ... I can tell because the startup
> > messages from USB are pretty minimal.  (See appended, vs what you sent...)
> > 
> > Please try again with USB debugging enabled.
> 
> Argh, silly me. Here you go (attached). It has not crashed yet with the 
> patch though.

You know, Dave, seeing all those

> ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021

lines in the log brings up some ideas that have been percolating in my 
mind for a while.  They have to do with the possibility of a race 
between the watchdog routine and assertion of IAA.

In fact, if the timing comes out just wrong then it's possible (on SMP
systems) for an IAA interrupt to arrive when the watchdog
routine has already started running.  Then end_unlink_async() might get 
called right at the start of a new IAA cycle, or when the reclaim list 
is empty.

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/