please help backporting some patches to stable release 23.11.6

please help backporting some patches to stable release 23.11.6

[Shani Peretz]

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 23.11
stable branch, as conflicts or build errors occur.

Can authors check your patches in the following list and either:
    - Backport your patches to the 23.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 12/28/25.

You can find the a temporary work-in-progress branch of the coming 23.11.6
release at:
    https://github.com/shanipr/dpdk-stable
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

Some notes on stable backports:

A backport should contain a reference to the DPDK main branch commit
in it's commit message in the following fashion:
    [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]

For example:
    https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 23.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 23.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 23.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Shani

---
b74d638ab9  Bruce Richardson test/func_reentrancy: fix args to EAL init call - will remove from need backport list
78ea4b4fcb  Gagandeep Singh  bus/dpaa: improve cleanup - new patch was sent and added to 23.11
7ba84453ba  Jasper Tran O'Leary net/gve: free device resources on close
f4a70b449b  Joshua Washington net/gve: add DQO Tx descriptor limit
92d330a3ea  Joshua Washington net/gve: clean when insufficient Tx descriptors
ee06313a50  Joshua Washington net/gve: send whole packet when mbuf is large
97e2e198b9  Nawal Kishor     rawdev: fix device ID retrieval failure handling
820ca7361b  Rongwei Liu      net/mlx5: fix flow aging race condition
74348d7ad2  Vamsi Attunuru   net/octeon_ep: fix mbuf data offset update
f4905fdcf6  Vladimir Medvedkin fib6: fix memory leak on delete operation

RE: please help backporting some patches to stable release 23.11.6

[Shani Peretz]

Hi there,

Apologize for the inconvenience, but my previous email didn't include stable@dpdk.org in the CC list so your replies didn't reach there. If you don't mind, please resend your reply to this email.
Thank you and sorry.

Best regards, 
Shani

> -----Original Message-----
> From: Shani Peretz <shperetz@nvidia.com>
> Sent: Tuesday, 23 December 2025 10:24
> To: dpdk stable <stable@dpdk.org>
> Cc: Anatoly Burakov <anatoly.burakov@intel.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; Ankit Garg <nktgrg@google.com>; Bruce
> Richardson <bruce.richardson@intel.com>; Chengwen Feng
> <fengchengwen@huawei.com>; Ciara Loftus <ciara.loftus@intel.com>;
> Cunming Liang <cunming.liang@intel.com>; Dariusz Sosnowski
> <dsosnowski@nvidia.com>; David Marchand
> <david.marchand@redhat.com>; Gagandeep Singh <g.singh@nxp.com>;
> Haiyue Wang <haiyue.wang@intel.com>; Hemant Agrawal
> <hemant.agrawal@nxp.com>; Honnappa Nagarahalli
> <honnappa.nagarahalli@arm.com>; Jasper Tran O'Leary
> <jtranoleary@google.com>; Jeroen de Borst <jeroendb@google.com>; Joshua
> Washington <joshwash@google.com>; Junfeng Guo <junfengg@nvidia.com>;
> Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>; Matan Azrad
> <matan@nvidia.com>; Michael Baum <michaelba@nvidia.com>; Morten
> Brørup <mb@smartsharesystems.com>; Nawal Kishor
> <nkishor@marvell.com>; Ori Kam <orika@nvidia.com>; Robin Jarry
> <rjarry@redhat.com>; rongwei liu <rongweil@nvidia.com>; Rushil Gupta
> <rushilg@google.com>; Sachin Saxena <sachin.saxena@nxp.com>; Sameh
> Gobriel <sameh.gobriel@intel.com>; Shreyansh Jain
> <shreyansh.jain@nxp.com>; Suanming Mou <suanmingm@nvidia.com>;
> NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>;
> Vamsi Attunuru <vattunuru@marvell.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Vladimir Medvedkin
> <vladimir.medvedkin@intel.com>; Xiaoyun Li <xiaoyun.li@intel.com>; Yipeng
> Wang <yipeng1.wang@intel.com>; Zhe Tao <zhe.tao@intel.com>; Shani Peretz
> <shperetz@nvidia.com>
> Subject: please help backporting some patches to stable release 23.11.6
> 
> Hi commit authors (and maintainers),
> 
> Despite being selected by the DPDK maintenance tool ./devtools/git-log-
> fixes.sh I didn't apply following commits from DPDK main to 23.11 stable
> branch, as conflicts or build errors occur.
> 
> Can authors check your patches in the following list and either:
>     - Backport your patches to the 23.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 12/28/25.
> 
> You can find the a temporary work-in-progress branch of the coming 23.11.6
> release at:
>     https://github.com/shanipr/dpdk-stable
> It is recommended to backport on top of that to minimize further conflicts or
> misunderstandings.
> 
> Some notes on stable backports:
> 
> A backport should contain a reference to the DPDK main branch commit in it's
> commit message in the following fashion:
>     [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]
> 
> For example:
>     https://git.dpdk.org/dpdk-
> stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb
> 
> When sending the backported patch, please indicate the target branch in the
> subject line, as we have multiple branches, for example:
>     [PATCH 23.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 23.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 23.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Shani
> 
> ---
> b74d638ab9  Bruce Richardson test/func_reentrancy: fix args to EAL init call -
> will remove from need backport list 78ea4b4fcb  Gagandeep Singh  bus/dpaa:
> improve cleanup - new patch was sent and added to 23.11 7ba84453ba
> Jasper Tran O'Leary net/gve: free device resources on close f4a70b449b
> Joshua Washington net/gve: add DQO Tx descriptor limit 92d330a3ea  Joshua
> Washington net/gve: clean when insufficient Tx descriptors
> ee06313a50  Joshua Washington net/gve: send whole packet when mbuf is
> large
> 97e2e198b9  Nawal Kishor     rawdev: fix device ID retrieval failure handling
> 820ca7361b  Rongwei Liu      net/mlx5: fix flow aging race condition
> 74348d7ad2  Vamsi Attunuru   net/octeon_ep: fix mbuf data offset update
> f4905fdcf6  Vladimir Medvedkin fib6: fix memory leak on delete operation

please help backporting some patches to stable release 23.11.6

[Shani Peretz]

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 23.11
stable branch, as conflicts or build errors occur.

Can authors check your patches in the following list and either:
    - Backport your patches to the 23.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 12/31/25.

You can find the a temporary work-in-progress branch of the coming 23.11.6
release at:
    https://github.com/shanipr/dpdk-stable
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

Some notes on stable backports:

A backport should contain a reference to the DPDK main branch commit
in it's commit message in the following fashion:
    [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]

For example:
    https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 23.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 23.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 23.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Shani

---
8a8c02d2bb  Anatoly Burakov  vfio: fix custom containers in multiprocess
bd96307d15  Bruce Richardson net/fm10k: fix Tx packet prepare
19d7188f6f  Bruce Richardson net/ixgbe: fix Tx packet prepare
12b050defa  Chengwen Feng    app/dma-perf: check buffer size
cca4c3bc3f  Chengwen Feng    app/dma-perf: fix stopping device
431bc9c42e  Ciara Loftus     net/iavf: remove extra stores in AVX-512 VLAN offload
0e3c389b9e  Gagandeep Singh  bus/dpaa: do proper cleanup of frame queues on shutdown
7ba84453ba  Jasper Tran O'Leary net/gve: free device resources on close
6280a30607  Jiawen Wu        net/ngbe: fix checksum error counter
02c9cc1012  Jiawen Wu        net/txgbe: filter FDIR match flex bytes for tunnel
b9ad8a6e72  Jiawen Wu        net/txgbe: fix checksum error counter
c9a341034a  Jiawen Wu        net/txgbe: fix FDIR filter for SCTP tunnel
a2d4de2710  Jiawen Wu        net/txgbe: fix FDIR input mask
f9465bdcef  Jun Yang         net/dpaa2: fix error frame dump
97e2e198b9  Nawal Kishor     rawdev: fix device ID retrieval failure handling
327682174e  Nupur Uttarwar   net/mlx5: skip Rx control flow tables in isolated mode
4f0abf4b7e  Prashant Gupta   net/dpaa2: free buffers from error queue
253174309f  Radu Nicolau     crypto/qat: fix source buffer alignment
820ca7361b  Rongwei Liu      net/mlx5: fix flow aging race condition
3eec7a797f  Rongwei Liu      net/mlx5: remove counter alignment
d762a8fbbd  Satheesh Paul    net/cnxk: fix port ID default action
743bbd3bd2  Sunil Kumar Kori net/ice: fix Tx packet prepare
74348d7ad2  Vamsi Attunuru   net/octeon_ep: fix mbuf data offset update
f4905fdcf6  Vladimir Medvedkin fib6: fix memory leak on delete operation

RE: please help backporting some patches to stable release 23.11.6

[Shani Peretz]

> -----Original Message-----
> From: Richardson, Bruce <bruce.richardson@intel.com>
> Sent: Monday, 22 December 2025 10:42
> To: dpdk stable <stable@dpdk.org>
> Subject: RE: please help backporting some patches to stable release 23.11.6
> 
> External email: Use caution opening links or attachments
> 
> 
> > -----Original Message-----
> > From: Shani Peretz <shperetz@nvidia.com>
> > Sent: Sunday, December 21, 2025 4:26 PM
> > Cc: Burakov, Anatoly <anatoly.burakov@intel.com>; Andrew Rybchenko
> > <andrew.rybchenko@oktetlabs.ru>; Ankit Garg <nktgrg@google.com>;
> > Richardson, Bruce <bruce.richardson@intel.com>; Chengwen Feng
> > <fengchengwen@huawei.com>; Loftus, Ciara <ciara.loftus@intel.com>;
> > Cunming Liang <cunming.liang@intel.com>; Dariusz Sosnowski
> > <dsosnowski@nvidia.com>; Marchand, David
> <david.marchand@redhat.com>;
> > Gagandeep Singh <g.singh@nxp.com>; Haiyue Wang
> > <haiyue.wang@intel.com>; Hemant Agrawal <hemant.agrawal@nxp.com>;
> > Nagarahalli, Honnappa <Honnappa.Nagarahalli@arm.com>; Jasper Tran
> > O'Leary <jtranoleary@google.com>; Jeroen de Borst
> > <jeroendb@google.com>; Joshua Washington <joshwash@google.com>;
> > Junfeng Guo <junfengg@nvidia.com>; Konstantin Ananyev
> > <konstantin.v.ananyev@yandex.ru>; Matan Azrad <matan@nvidia.com>;
> > Michael Baum <michaelba@nvidia.com>; Morten Brørup
> > <mb@smartsharesystems.com>; Nawal Kishor <nkishor@marvell.com>; Ori
> > Kam <orika@nvidia.com>; Robin Jarry <rjarry@redhat.com>; Rongwei Liu
> > <rongweil@nvidia.com>; Rushil Gupta <rushilg@google.com>; Sachin
> > Saxena <sachin.saxena@nxp.com>; Gobriel, Sameh
> > <sameh.gobriel@intel.com>; Shreyansh Jain <shreyansh.jain@nxp.com>;
> > Suanming Mou <suanmingm@nvidia.com>; Thomas Monjalon
> > <thomas@monjalon.net>; Vamsi Attunuru <vattunuru@marvell.com>;
> > Viacheslav Ovsiienko <viacheslavo@nvidia.com>; Medvedkin, Vladimir
> > <vladimir.medvedkin@intel.com>; Xiaoyun Li <xiaoyun.li@intel.com>;
> > Wang, Yipeng1 <yipeng1.wang@intel.com>; Zhe Tao <zhe.tao@intel.com>
> > Subject: please help backporting some patches to stable release
> > 23.11.6
> >
> > Hi commit authors (and maintainers),
> >
> > Despite being selected by the DPDK maintenance tool
> > ./devtools/git-log- fixes.sh I didn't apply following commits from
> > DPDK main to 23.11 stable branch, as conflicts or build errors occur.
> >
> > Can authors check your patches in the following list and either:
> >     - Backport your patches to the 23.11 branch, or
> >     - Indicate that the patch should not be backported
> >
> > Please do either of the above by 12/28/25.
> >
> > You can find the a temporary work-in-progress branch of the coming
> > 23.11.6 release at:
> >     https://github.com/shanipr/dpdk-stable
> > It is recommended to backport on top of that to minimize further
> > conflicts or misunderstandings.
> >
> > Some notes on stable backports:
> >
> > A backport should contain a reference to the DPDK main branch commit
> > in it's commit message in the following fashion:
> >     [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]
> >
> > For example:
> >     https://git.dpdk.org/dpdk-
> >
> stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb
> >
> > When sending the backported patch, please indicate the target branch
> > in the subject line, as we have multiple branches, for example:
> >     [PATCH 23.11] foo/bar: fix baz
> >
> > With git format-patch, this can be achieved by appending the parameter:
> >     --subject-prefix='PATCH 23.11'
> >
> > Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> >
> > FYI, branch 23.11 is located at tree:
> >    https://git.dpdk.org/dpdk-stable
> >
> > Thanks.
> >
> > Shani
> >
> > ---
> > b74d638ab9  Bruce Richardson test/func_reentrancy: fix args to EAL
> > init call
> 
> Since this is a patch to unit tests only, and hasn't been causing us any issues
> before, I don't think we need it backported.
> 
> /Bruce

Thanks Bruce, will remove from need backport list

RE: please help backporting some patches to stable release 23.11.6

[Richardson, Bruce]

> -----Original Message-----
> From: Shani Peretz <shperetz@nvidia.com>
> Sent: Sunday, December 21, 2025 4:26 PM
> Cc: Burakov, Anatoly <anatoly.burakov@intel.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; Ankit Garg <nktgrg@google.com>;
> Richardson, Bruce <bruce.richardson@intel.com>; Chengwen Feng
> <fengchengwen@huawei.com>; Loftus, Ciara <ciara.loftus@intel.com>;
> Cunming Liang <cunming.liang@intel.com>; Dariusz Sosnowski
> <dsosnowski@nvidia.com>; Marchand, David
> <david.marchand@redhat.com>; Gagandeep Singh <g.singh@nxp.com>;
> Haiyue Wang <haiyue.wang@intel.com>; Hemant Agrawal
> <hemant.agrawal@nxp.com>; Nagarahalli, Honnappa
> <Honnappa.Nagarahalli@arm.com>; Jasper Tran O'Leary
> <jtranoleary@google.com>; Jeroen de Borst <jeroendb@google.com>; Joshua
> Washington <joshwash@google.com>; Junfeng Guo <junfengg@nvidia.com>;
> Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>; Matan Azrad
> <matan@nvidia.com>; Michael Baum <michaelba@nvidia.com>; Morten
> Brørup <mb@smartsharesystems.com>; Nawal Kishor
> <nkishor@marvell.com>; Ori Kam <orika@nvidia.com>; Robin Jarry
> <rjarry@redhat.com>; Rongwei Liu <rongweil@nvidia.com>; Rushil Gupta
> <rushilg@google.com>; Sachin Saxena <sachin.saxena@nxp.com>; Gobriel,
> Sameh <sameh.gobriel@intel.com>; Shreyansh Jain
> <shreyansh.jain@nxp.com>; Suanming Mou <suanmingm@nvidia.com>;
> Thomas Monjalon <thomas@monjalon.net>; Vamsi Attunuru
> <vattunuru@marvell.com>; Viacheslav Ovsiienko <viacheslavo@nvidia.com>;
> Medvedkin, Vladimir <vladimir.medvedkin@intel.com>; Xiaoyun Li
> <xiaoyun.li@intel.com>; Wang, Yipeng1 <yipeng1.wang@intel.com>; Zhe Tao
> <zhe.tao@intel.com>
> Subject: please help backporting some patches to stable release 23.11.6
> 
> Hi commit authors (and maintainers),
> 
> Despite being selected by the DPDK maintenance tool ./devtools/git-log-
> fixes.sh
> I didn't apply following commits from DPDK main to 23.11
> stable branch, as conflicts or build errors occur.
> 
> Can authors check your patches in the following list and either:
>     - Backport your patches to the 23.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 12/28/25.
> 
> You can find the a temporary work-in-progress branch of the coming 23.11.6
> release at:
>     https://github.com/shanipr/dpdk-stable
> It is recommended to backport on top of that to minimize further conflicts or
> misunderstandings.
> 
> Some notes on stable backports:
> 
> A backport should contain a reference to the DPDK main branch commit
> in it's commit message in the following fashion:
>     [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]
> 
> For example:
>     https://git.dpdk.org/dpdk-
> stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb
> 
> When sending the backported patch, please indicate the target branch in the
> subject line, as we have multiple branches, for example:
>     [PATCH 23.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 23.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 23.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Shani
> 
> ---
> b74d638ab9  Bruce Richardson test/func_reentrancy: fix args to EAL init call

Since this is a patch to unit tests only, and hasn't been causing us any issues before, I don't think we need it backported.

/Bruce