please help backporting some patches to stable release 24.11.4

please help backporting some patches to stable release 24.11.4

[Kevin Traynor]

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 11/27/25.

You can find the a temporary work-in-progress branch of the coming 24.11.4
release at:
    https://github.com/kevintraynor/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.

Kevin

---
f2f75ffe14  Viacheslav Ovsiienko net/mlx5/hws: fix ESP header match in strict mode
08b83e84e1  Nithinsen Kaithakadan crypto/cnxk: fix TLS mbuf
8a8c02d2bb  Anatoly Burakov  vfio: fix custom containers in multiprocess
d1b3b66967  Chengwen Feng    app/dma-perf: fix on-flight DMA when verifying data
cca4c3bc3f  Chengwen Feng    app/dma-perf: fix stopping device
0e3c389b9e  Gagandeep Singh  bus/dpaa: do proper cleanup of frame queues on shutdown
822bd84cea  Howard Wang      net/r8169: fix static analysis warnings
431bc9c42e  Ciara Loftus     net/iavf: remove extra stores in AVX-512 VLAN offload
3bf9f0f9f0  Viacheslav Ovsiienko net/mlx5: fix control flow leakage for external SQ
a4ad0eba9d  Wathsala Vithanage ring: establish safe partial order in default mode
66d5f96278  Wathsala Vithanage ring: establish safe partial order in HTS mode
36b69b5f95  Wathsala Vithanage ring: establish safe partial order in RTS mode

743bbd3bd2  Sunil Kumar Kori net/ice: fix Tx packet prepare
19d7188f6f  Bruce Richardson net/ixgbe: fix Tx packet prepare
bd96307d15  Bruce Richardson net/fm10k: fix Tx packet prepare
^^^ These seem to need:
    066f3d9cc21c ("ethdev: remove callback checks from fast path")
but I'm not sure if we should backport that (also it doesn apply cleanly)

5a753913e0  Monendra Singh Kushwaha common/cnxk: fix inline device write operation
860f6c63db  Maayan Kashani   net/mlx5: fix device start error handling

please help backporting some patches to stable release 24.11.4

[Kevin Traynor]

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 11/05/25.

You can find the a temporary work-in-progress branch of the coming 24.11.4
release at:
    https://github.com/kevintraynor/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.

Kevin

---
44d6571092  Dariusz Sosnowski net/mlx5: fix min and max MTU reporting
f2f75ffe14  Viacheslav Ovsiienko net/mlx5/hws: fix ESP header match in strict mode
08b83e84e1  Nithinsen Kaithakadan crypto/cnxk: fix TLS mbuf
89b634c9cf  Dean Marx        dts: add reception check to checksum suite