[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1452135122.2768.159.camel@decadent.org.uk>
Date: Thu, 07 Jan 2016 02:52:02 +0000
From: Ben Hutchings <ben@...adent.org.uk>
To: Kamal Mostafa <kamal@...onical.com>,
Luis Henriques <luis.henriques@...onical.com>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
kernel-team@...ts.ubuntu.com,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 4.2.y-ckt 009/211] xhci: don't finish a TD if we get a
short transfer event mid TD
On Wed, 2016-01-06 at 11:55 -0800, Kamal Mostafa wrote:
> On Wed, 2016-01-06 at 17:05 +0000, Ben Hutchings wrote:
> > On Tue, 2016-01-05 at 11:41 -0800, Kamal Mostafa wrote:
> > > 4.2.8-ckt1 -stable review patch. If anyone has any objections, please let me know.
> > >
> > > ------------------
> > >
> > > From: Mathias Nyman <mathias.nyman@...ux.intel.com>
> > >
> > > commit e210c422b6fdd2dc123bedc588f399aefd8bf9de upstream.
> > >
> > > If the difference is big enough between the bytes asked and received
> > > in a bulk transfer we can get a short transfer event pointing to a TRB in
> > > the middle of the TD. We don't want to handle the TD yet as we will anyway
> > > receive a new event for the last TRB in the TD.
> > >
> > > Hold off from finishing the TD and removing it from the list until we
> > > receive an event for the last TRB in the TD
> > >
> > > Signed-off-by: Mathias Nyman <mathias.nyman@...ux.intel.com>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > > [ kamal: backport to 4.2-stable: context ]
> > > Signed-off-by: Kamal Mostafa <kamal@...onical.com>
> > [...]
> >
> > This causes regressions (see https://bugs.debian.org/808602 and
> > https://bugs.debian.org/808953 ) so please hold off until there's a
> > complete fix upstream.
>
> Thanks for the heads-up, Ben. I'll defer it for 4.2-stable.
>
> I'm thinking that it should also be reverted from the stable kernels
> that already carry it (3.2, 3.13, 3.16, 3.19), unless that complete
> upstream fix is really imminent. Is it?
Normally if there's a regression that affects both mainline and stable
branches, we wait for it to be fixed in mainline first.
Ben.
--
Ben Hutchings
Life would be so much easier if we could look at the source code.
Download attachment "signature.asc" of type "application/pgp-signature" (812 bytes)
Powered by blists - more mailing lists