patch 'net/mlx5: fix port event cleaning order' has been queued to stable release 20.11.7

Michael Baum michaelba at nvidia.com
Mon Nov 21 21:36:54 CET 2022


Hi,

> 
> On Monday, 2022-11-21 at 16:12, Luca Boccassi wrote:
> >
> > On Sun, 20 Nov 2022 at 07:28, Michael Baum <michaelba at nvidia.com> wrote:
> > >
> > > On Fri, 2022-11-18 at 16:28, Luca Boccassi wrote:
> > > >
> > > > On Fri, 2022-11-18 at 12:53 +0000, Michael Baum wrote:
> > > > > Hi Luca,
> > > > >
> > > > > This patch causes another issue, so I have sent another patch to
> > > > > squash
> > into.
> > > > >
> > > > > The title of this patch is: " [PATCH 20.11] net/mlx5: fix
> > > > > invalid memory access
> > > > in port closing"
> > > > >
> > > > > Thanks,
> > > > > Michael Baum
> > > >
> > > > Is it a backport gone wrong (or an issue specific to 20.11), or is
> > > > it an issue also in the same change that went in main? If the
> > > > latter, what's the commit id of the fix?
> > >
> > > The issue also in the same change that went in main.
> > > I sent the fix and it isn't merged yet, the fix in patchwork:
> > > https://patchwork.dpdk.org/project/dpdk/patch/20221117152807.1259256
> > > -1
> > > -michaelba at nvidia.com/
> >
> > Is this going to be pulled in 22.11?
> 
> Yes, it has been already taken into next-net-mlx.

The commit id in main is  ef4ece4dbb962e38c19579766203c21a20622df9


More information about the stable mailing list