linux-kernel - Re: [REVERT][v3.x.y] EHCI: Update qTD next pointer in QH overlay region during unlink

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: <510C4700.5030304@canonical.com>
Date:	Fri, 01 Feb 2013 17:51:44 -0500
From:	Joseph Salisbury <joseph.salisbury@...onical.com>
To:	Alan Stern <stern@...land.harvard.edu>
CC:	Ben Hutchings <ben@...adent.org.uk>,
	LKML <linux-kernel@...r.kernel.org>, pkondeti@...eaurora.org,
	Greg KH <gregkh@...uxfoundation.org>,
	Herton Krzesinski <herton.krzesinski@...onical.com>,
	stable@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [REVERT][v3.x.y] EHCI: Update qTD next pointer in QH overlay
 region during unlink

On 01/17/2013 01:56 PM, Alan Stern wrote:
> On Thu, 17 Jan 2013, Joseph Salisbury wrote:
>
>> Hello,
>>
>> Please consider reverting commit
>> 3d037774b42ed677f699b1dce7d548d55f4e4c2b in mainline as well as in the
>> current stable releases.  It was included upstream as of v3.6-rc6.  This
>> commit introduced a regression, described in the following bug report:
>>
>> http://bugs.launchpad.net/bugs/1088733
>>
>> Reverting commit 3d037774b42ed677f699b1dce7d548d55f4e4c2b in the v3.2
>> kernel has been confirmed to resolve the aforementioned bug.
> I do not want to revert this commit without first understanding what is
> going wrong.  Please ask the reporter to post usbmon traces showing
> what happens in both a failed and a successful recording attempt.
>
> Alan Stern
>
Hi Alan,

There is a tar file[0] attached to the bug report[1].  The tar file 
contains a few examples of failed and successful recording attempts 
while collecting usbmon traces.  There is a readme.txt file available 
after extracting the files.

The bug reporter states that only the first recording after boot fails. 
Subsequent recordings succeed will succeed.

Thanks again for reviewing this, Alan.  Just let me know if you would 
like any additional data or testing.

Thanks,

Joe

[0] 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088733/+attachment/3510887/+files/usbmon-1088733.tar.gz
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088733
--
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/