linux-kernel - Re: [PATCH] usb: xhci: fix config fail of FS hub behind a HS hub with MTT

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:	Fri, 04 Dec 2015 14:06:30 +0200
From:	Mathias Nyman <mathias.nyman@...el.com>
To:	Chunfeng Yun <chunfeng.yun@...iatek.com>
CC:	Matthias Brugger <matthias.bgg@...il.com>,
	Felipe Balbi <balbi@...com>, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-usb@...r.kernel.org,
	linux-mediatek@...ts.infradead.org,
	Daniel Kurtz <djkurtz@...omium.org>,
	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] usb: xhci: fix config fail of FS hub behind a HS hub
 with MTT

On 03.12.2015 08:14, Chunfeng Yun wrote:
> if a full speed hub connects to a high speed hub which
> supports MTT, the MTT field of its slot context will be set
> to 1 when xHCI driver setups an xHCI virtual device in
> xhci_setup_addressable_virt_dev(); once usb core fetch its
> hub descriptor, and need to update the xHC's internal data
> structures for the device, the HUB field of its slot context
> will be set to 1 too, meanwhile MTT is also set before,
> this will cause configure endpoint command fail, so in the
> case, we should clear MTT to 0 for full speed hub according
> to section 6.2.2
>
> Signed-off-by: Chunfeng Yun <chunfeng.yun@...iatek.com>
> ---

Thanks, patch added to queue

-Mathias
--
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/