On 17.02.22 08:29, Greg KH wrote: > On Thu, Feb 17, 2022 at 02:38:08PM +0800, liqiong wrote: >> Upstream has no this bug. > > What do you mean by this? > > confused, Dito. If this is fixed upstream and broken in stable kernels, we'd want either a backport of the relevant upstream fix, or if too complicated, a stable-only fix. -- Thanks, David / dhildenb