[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhTjFMw111-fyZsFaCSnN3b-TuQjqXcc1zVu2QTTekTohw@mail.gmail.com>
Date: Mon, 30 Aug 2021 10:20:22 -0400
From: Paul Moore <paul@...l-moore.com>
To: Dongliang Mu <mudongliangabcd@...il.com>,
王贇 <yun.wang@...ux.alibaba.com>
Cc: Sasha Levin <sashal@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
stable@...r.kernel.org, Abaci <abaci@...ux.alibaba.com>,
"David S . Miller" <davem@...emloft.net>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 5.13 13/14] net: fix NULL pointer reference in cipso_v4_doi_free
On Mon, Aug 30, 2021 at 8:42 AM Dongliang Mu <mudongliangabcd@...il.com> wrote:
>
> On Mon, Aug 30, 2021 at 8:01 PM Sasha Levin <sashal@...nel.org> wrote:
> >
> > From: 王贇 <yun.wang@...ux.alibaba.com>
> >
> > [ Upstream commit 733c99ee8be9a1410287cdbb943887365e83b2d6 ]
> >
>
> Hi Sasha,
>
> Michael Wang has sent a v2 patch [1] for this bug and it is merged
> into netdev/net-next.git. However, the v1 patch is already in the
> upstream tree.
>
> How do you guys handle such a issue?
>
> [1] https://lkml.org/lkml/2021/8/30/229
Ugh. Michael can you please work with netdev to fix this in the
upstream, and hopefully -stable, kernels? My guess is you will need
to rebase your v2 patch on top of the v1 patch (basically what exists
in upstream) and send that back out.
--
paul moore
www.paul-moore.com
Powered by blists - more mailing lists