[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPNVh5c88ZSAuhjdpf6_AULufZqjSkjWB7W8tguKzRTwYJbTWA@mail.gmail.com>
Date: Fri, 3 May 2019 08:58:59 -0700
From: Peter Oskolkov <posk@...gle.com>
To: Eric Dumazet <edumazet@...gle.com>
Cc: "David S . Miller" <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
Eric Dumazet <eric.dumazet@...il.com>,
Stfan Bader <stefan.bader@...onical.com>,
Florian Westphal <fw@...len.de>
Subject: Re: [PATCH net] ip6: fix skb leak in ip6frag_expire_frag_queue()
On Fri, May 3, 2019 at 8:52 AM Eric Dumazet <edumazet@...gle.com> wrote:
>
> On Fri, May 3, 2019 at 11:33 AM Peter Oskolkov <posk@...gle.com> wrote:
> >
> > This skb_get was introduced by commit 05c0b86b9696802fd0ce5676a92a63f1b455bdf3
> > "ipv6: frags: rewrite ip6_expire_frag_queue()", and the rbtree patch
> > is not in 4.4, where the bug is reported at.
> > Shouldn't the "Fixes" tag also reference the original patch?
>
> No, this bug really fixes a memory leak.
>
> Fact that it also fixes the XFRM issue is secondary, since all your
> patches are being backported in stable
> trees anyway for other reasons.
There are no plans to backport rbtree patches to 4.4 and earlier at
the moment, afaik.
>
> There is no need to list all commits and give a complete context for a
> bug fix like this one,
> this would be quite noisy.
Powered by blists - more mailing lists