[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YJpqJr/3XEIYrtko@kroah.com>
Date: Tue, 11 May 2021 13:27:34 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Chunfeng Yun <chunfeng.yun@...iatek.com>
Cc: Alan Stern <stern@...land.harvard.edu>,
Matthias Brugger <matthias.bgg@...il.com>,
Thinh Nguyen <Thinh.Nguyen@...opsys.com>,
"Gustavo A . R . Silva" <gustavoars@...nel.org>,
Bixuan Cui <cuibixuan@...wei.com>,
Eugeniu Rosca <erosca@...adit-jv.com>,
Oliver Neukum <oneukum@...e.com>, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Tianping Fang <tianping.fang@...iatek.com>,
Eddie Hung <eddie.hung@...iatek.com>,
Ikjoon Jang <ikjn@...omium.org>
Subject: Re: [PATCH] usb: core: hub: fix race condition about TRSMRCY of
resume
On Tue, May 11, 2021 at 06:15:22PM +0800, Chunfeng Yun wrote:
> This may happen if the port becomes resume status exactly
> when usb_port_resume() gets port status, it still need provide
> a TRSMCRY time before access the device.
>
> Reported-by: Tianping Fang <tianping.fang@...iatek.com>
> Signed-off-by: Chunfeng Yun <chunfeng.yun@...iatek.com>
> ---
> drivers/usb/core/hub.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Does this need to go to any older/stable kernels? If so, how far back?
thanks,
greg k-h
Powered by blists - more mailing lists