Re: [dpdk-stable] It there plan to queue this patch to stable release 19.11.9

[Thomas Monjalon <thomas@monjalon.net>]

31/05/2021 11:21, Christian Ehrhardt:
> On Wed, May 26, 2021 at 5:13 AM Yu, DapengX <dapengx.yu@intel.com> wrote:
> > This patch: http://mails.dpdk.org/archives/stable/2021-March/029204.html
> 
> This patch actually was never merged in the main branch
> On main we have:
> 
> commit f93949c3afc39b0f610e0661f7baa21060ada13a
> Author: Haiyue Wang <haiyue.wang@intel.com>
> net/ice: fix memory leak on dev closed
> 
> This one also refers to bd513ece3c40 for a fix and was in 19.11 already.
> Then quite similar to what you referred to, but a more generic (all
> drivers) fix on the main branch
> 
> commit 30410493759f4bae3f65497737661e27b93c2d0e
> Author: Thomas Monjalon <thomas@monjalon.net>
> drivers/net: check process type in close operation
> See => https://github.com/DPDK/dpdk/commit/30410493759f4bae3f65497737661e27b93c2d0e
> 
> This one was in 20.11 but not targeted for stable@dpdk.org
> 
> The patch almost applies but since the change is mostly the same to
> all drivers it seems backportable.
> 
> Maybe if you could sync with Thomas if this (general) solution is
> applicable and prepare the backport we can add it.
> It is close as I wanted to call for RC1 already, but if done soon it
> should be fine.
> I'll hold back 19.11.9-RC1 another day to give this a chance to be
> clarified until tomorrow.
> 
> @Dapeng please talk to Thomas and consider providing a 19.11.9
> backport of the fix that made it into the main branch.
> @Thomas Monjalon was there a specific reason/prereq which made you not
> targeting stable@ with the fix?

It was not considered as a fix but a behaviour improvement :)
I agree it could be backported.