please help backporting some patches to stable release 24.11.5

please help backporting some patches to stable release 24.11.5

[luca.boccassi]

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 24.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 24.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 02/27/26.

You can find the a temporary work-in-progress branch of the coming 24.11.5
release at:
    https://github.com/bluca/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 24.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
f82b3ed6ab  Anatoly Burakov  net/ixgbe: fix pointer handling in IPsec
ab797d5bcf  Bruce Richardson dma/idxd: mark portal pointer as volatile
77bb34e047  Ivan Malov       net/sfc: avoid speed reset when setting FEC in started state
e0f92e31f7  Kishore Padmanabha net/bnxt: fix statistics for high number of queues
bd2f563dbd  Rahul Bhansali   common/cnxk: fix duplicated branches
2e79349dcd  Song Yoong Siang net/e1000: fix igc launch time calculation

RE: please help backporting some patches to stable release 24.11.5

[Kishore Padmanabha]

[-- Attachment #1: Type: text/plain, Size: 2444 bytes --]

Hi Luca,

The patch e0f92e31f7 is not required to be backported to 24.11. There has
changes in that part of code that will not allow simple merge of this fix.
This fix is not critical to be ported to older version as it is fixing
stats counters in a specific scenario.

Thanks,
Kishore


-----Original Message-----
From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
Sent: Friday, February 20, 2026 10:41 AM
To: dpdk <dev@dpdk.org>
Cc: dpdk stable <stable@dpdk.org>
Subject: please help backporting some patches to stable release 24.11.5

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 24.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 24.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 02/27/26.

You can find the a temporary work-in-progress branch of the coming 24.11.5
release at:
    https://github.com/bluca/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=d90e6ae6f936ecdc2fd381
1ff9f26aec7f3c06eb

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

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

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

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

Thanks.

Luca Boccassi

---
f82b3ed6ab  Anatoly Burakov  net/ixgbe: fix pointer handling in IPsec
ab797d5bcf  Bruce Richardson dma/idxd: mark portal pointer as volatile
77bb34e047  Ivan Malov       net/sfc: avoid speed reset when setting FEC
in started state
e0f92e31f7  Kishore Padmanabha net/bnxt: fix statistics for high number of
queues
bd2f563dbd  Rahul Bhansali   common/cnxk: fix duplicated branches
2e79349dcd  Song Yoong Siang net/e1000: fix igc launch time calculation

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5493 bytes --]

please help backporting some patches to stable release 24.11.5

[luca.boccassi]

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 24.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 24.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 03/26/26.

You can find the a temporary work-in-progress branch of the coming 24.11.5
release at:
    https://github.com/bluca/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 24.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
2f7cdd821b  Dariusz Sosnowski net/mlx5: fix probing to allow BlueField Socket Direct
f741298f70  Long Li          net/netvsc: support multi-process VF device removal
5a9362386e  Stephen Hemminger examples/vmdq_dcb: initialize all configuration structures
abacc3b2da  Stephen Hemminger net/tap: fix handling of queue stats
c67f59508d  Stephen Hemminger net/tap: fix Rx descriptor vs scatter segment confusion
77f831b6f1  Stephen Hemminger pcapng: handle packets copied before file open
b3b8301dee  Thomas Monjalon  net/idpf: fix commas instead of semicolons
3ed9a05bff  Xavier Guillaume net/af_packet: fix receive buffer overflow

please help backporting some patches to stable release 24.11.5

[luca.boccassi]

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 24.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 24.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 2026/04/01.

You can find the a temporary work-in-progress branch of the coming 24.11.5
release at:
    https://github.com/bluca/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 24.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
874312e261  Patrick Robb     dts: avoid resources conflict on quick stop/start
bc15a33eee  Vipin Varghese   doc: update AMD EPYC guide

Re: please help backporting some patches to stable release 24.11.5

[Patrick Robb]

[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]

Hi Luca,

Will backport it to 24.11 and share back to you thanks.

On Thu, Mar 26, 2026 at 9:00 AM <luca.boccassi@gmail.com> wrote:

> 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 24.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 24.11 branch, or
>     - Indicate that the patch should not be backported
>
> Please do either of the above by 2026/04/01.
>
> You can find the a temporary work-in-progress branch of the coming 24.11.5
> release at:
>     https://github.com/bluca/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 24.11] foo/bar: fix baz
>
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 24.11'
>
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>
> FYI, branch 24.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
>
> Thanks.
>
> Luca Boccassi
>
> ---
> 874312e261  Patrick Robb     dts: avoid resources conflict on quick
> stop/start
> bc15a33eee  Vipin Varghese   doc: update AMD EPYC guide
>

[-- Attachment #2: Type: text/html, Size: 2769 bytes --]

please help backporting some patches to stable release 24.11.5

[luca.boccassi]

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 24.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 24.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 2026/04/03.

You can find the a temporary work-in-progress branch of the coming 24.11.5
release at:
    https://github.com/bluca/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 24.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
f9b31cf4a6  Maxime Leroy     net/dpaa2: fix Rx error queue memory leaks

Re: please help backporting some patches to stable release 24.11.5

[Patrick Robb]

[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]

Hi Luca,

874312e261 does not need to be backported to 24.11, as the issue it fixes
only manifests when running cryptodev testing (which has only been added
during DPDK 26.03).

On Thu, Mar 26, 2026 at 9:00 AM <luca.boccassi@gmail.com> wrote:

> 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 24.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 24.11 branch, or
>     - Indicate that the patch should not be backported
>
> Please do either of the above by 2026/04/01.
>
> You can find the a temporary work-in-progress branch of the coming 24.11.5
> release at:
>     https://github.com/bluca/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 24.11] foo/bar: fix baz
>
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 24.11'
>
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>
> FYI, branch 24.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
>
> Thanks.
>
> Luca Boccassi
>
> ---
> 874312e261  Patrick Robb     dts: avoid resources conflict on quick
> stop/start
> bc15a33eee  Vipin Varghese   doc: update AMD EPYC guide
>

[-- Attachment #2: Type: text/html, Size: 2879 bytes --]