[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=XXPACnPt=5=7gH3L6DufZ4tLSPTN-AtTAmvi5KAJuP6A@mail.gmail.com>
Date: Tue, 17 Mar 2020 08:45:09 -0700
From: Doug Anderson <dianders@...omium.org>
To: Greg KH <greg@...ah.com>
Cc: "stable@...r.kernel.org" <stable@...r.kernel.org>,
Wen Gong <wgong@...eaurora.org>,
netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>, ath11k@...ts.infradead.org,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH v2] net: qrtr: fix len of skb_put_padto in qrtr_node_enqueue
Hi,
On Tue, Mar 17, 2020 at 3:26 AM Greg KH <greg@...ah.com> wrote:
>
> On Tue, Feb 25, 2020 at 02:52:24PM -0800, Doug Anderson wrote:
> > Hi,
> >
> >
> > On Sun, Jan 5, 2020 at 2:47 PM David Miller <davem@...emloft.net> wrote:
> > >
> > > From: Wen Gong <wgong@...eaurora.org>
> > > Date: Fri, 3 Jan 2020 12:50:16 +0800
> > >
> > > > The len used for skb_put_padto is wrong, it need to add len of hdr.
> > >
> > > Thanks, applied.
> >
> > I noticed this patch is in mainline now as:
> >
> > ce57785bf91b net: qrtr: fix len of skb_put_padto in qrtr_node_enqueue
> >
> > Though I'm not an expert on the code, it feels like a stable candidate
> > unless someone objects.
>
> Stable candidate for what tree(s)?
I noticed that it was lacking and applied cleanly on 5.4. As of
5.4.25 it's still not stable there. I only noticed it because I was
comparing all the patches in mainline in "net/qrtr" with what we had
in our tree and stumbled upon this one.
Looking at it a little more carefully, I guess you could say:
Fixes: e7044482c8ac ("net: qrtr: Pass source and destination to
enqueue functions")
...though it will be trickier to apply past commit 194ccc88297a ("net:
qrtr: Support decoding incoming v2 packets") just because the math
changed.
-Doug
Powered by blists - more mailing lists