please help backporting some patches to stable release 20.11.9

please help backporting some patches to stable release 20.11.9

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

Please do either of the above by 2023/07/21.

You can find the a temporary work-in-progress branch of the coming 20.11.9
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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
8b4618a7b4  Ciara Power      crypto/qat: fix null algorithm digest placement
d7d802daf8  Ferruh Yigit     app/testpmd: revert primary process polling all queues fix
5e170dd8b6  Jiawen Wu        net/txgbe: fix blocking system events
7cb939f648  Vikash Poddar    common/qat: detach crypto from compress build

RE: please help backporting some patches to stable release 20.11.9

[Jiawen Wu]

> 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 20.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 20.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 2023/07/21.
> 
> You can find the a temporary work-in-progress branch of the coming 20.11.9
> 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 20.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 20.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 20.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---


> 5e170dd8b6  Jiawen Wu        net/txgbe: fix blocking system events

Please drop this patch in stable 20.11.9, thanks.

please help backporting some patches to stable release 20.11.9

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

Please do either of the above by 07/27/23.

You can find the a temporary work-in-progress branch of the coming 20.11.9
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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
e6479f009f  Alexander Kozyrev net/mlx5: fix MPRQ stride size for headroom

please help backporting some patches to stable release 20.11.9

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

Please do either of the above by July 7th.

You can find the a temporary work-in-progress branch of the coming 20.11.9
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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
12011b11a3  Jiawen Wu        net/txgbe: adapt to MNG veto bit setting
646b058472  Jiawen Wu        net/txgbe: fix interrupt enable mask
141a520b35  Jie Hai          app/testpmd: fix primary process not polling all queues
6fd3a7a618  Mingjin Ye       net/ice/base: fix internal etype in switch filter

RE: please help backporting some patches to stable release 20.11.9

[Jiawen Wu]

> 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 20.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 20.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by July 7th.
> 
> You can find the a temporary work-in-progress branch of the coming 20.11.9
> 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 20.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 20.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 20.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---
> 12011b11a3  Jiawen Wu        net/txgbe: adapt to MNG veto bit setting
> 646b058472  Jiawen Wu        net/txgbe: fix interrupt enable mask

No need to backport these two patches for txgbe, thanks.

> 141a520b35  Jie Hai          app/testpmd: fix primary process not polling all queues
> 6fd3a7a618  Mingjin Ye       net/ice/base: fix internal etype in switch filter
> 

please help backporting some patches to stable release 20.11.9

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

Please do either of the above by 2023/06/23.

You can find the a temporary work-in-progress branch of the coming 20.11.9
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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
e97738919c  Chaoyong He      net/nfp: fix Tx descriptor free logic of NFD3
c1f0cdae14  Dariusz Sosnowski net/mlx5: fix drop action attribute validation
db42a84233  Dengdui Huang    app/testpmd: fix crash with invalid queue
0622428215  Jie Hai          net/hns3: fix missing FEC capability
cd41a27154  Jie Hai          net/hns3: get FEC capability from firmware
ad4d51d277  Rongwei Liu      net/mlx5: forbid duplicated tag index in pattern template
7ae50175c7  Saoirse O'Donovan test/crypto: fix return value for SNOW3G

RE: please help backporting some patches to stable release 20.11.9

[Rongwei Liu]

Hi Luca:
	Sorry for the mis-understanding.
	Below patch doesn't fit DPDK 20.11 branch while it's for 22.11 backport:
	"ad4d51d277"  "Rongwei Liu  net/mlx5: forbid duplicated tag index in pattern template"

BR
Rongwei

> -----Original Message-----
> From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> Sent: Thursday, June 15, 2023 09:38
> To: dpdk stable <stable@dpdk.org>
> Cc: Aaron Conole <aconole@redhat.com>; Alejandro Lucero
> <alejandro.lucero@netronome.com>; Anatoly Burakov
> <anatoly.burakov@intel.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; Beilei Xing <beilei.xing@intel.com>;
> Bernard Iremonger <bernard.iremonger@intel.com>; Bruce Richardson
> <bruce.richardson@intel.com>; Chaoyong He <chaoyong.he@corigine.com>;
> Chengchang Tang <tangchengchang@huawei.com>; Chengwen Feng
> <fengchengwen@huawei.com>; Ciara Power <ciara.power@intel.com>;
> Dariusz Sosnowski <dsosnowski@nvidia.com>; David Marchand
> <david.marchand@redhat.com>; Declan Doherty <declan.doherty@intel.com>;
> Dengdui Huang <huangdengdui@huawei.com>; Dongdong Liu
> <liudongdong3@huawei.com>; Ferruh Yigit <ferruh.yigit@amd.com>; Ferruh
> Yigit <ferruh.yigit@intel.com>; Heinrich Kuhn
> <heinrich.kuhn@netronome.com>; Honnappa Nagarahalli
> <honnappa.nagarahalli@arm.com>; Ilyes Ben Hamouda
> <ilyes.ben_hamouda@6wind.com>; Jiawei(Jonny) Wang
> <jiaweiw@nvidia.com>; Jie Hai <haijie1@huawei.com>; Kai Ji
> <kai.ji@intel.com>; Kiran Kumar K <kirankumark@marvell.com>; Lijun Ou
> <oulijun@huawei.com>; Matan Azrad <matan@nvidia.com>; Michael Santana
> <maicolgabriel@hotmail.com>; Min Hu (Connor) <humin29@huawei.com>;
> Morten Brørup <mb@smartsharesystems.com>; Niklas Söderlund
> <niklas.soderlund@corigine.com>; Olivier Matz <olivier.matz@6wind.com>;
> Ori Kam <orika@nvidia.com>; Rongwei Liu <rongweil@nvidia.com>; Saoirse
> O'Donovan <saoirse.odonovan@intel.com>; Shahaf Shuler
> <shahafs@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Wei Hu (Xavier)
> <xavier.huwei@huawei.com>; Wenzhuo Lu <wenzhuo.lu@intel.com>; Yisen
> Zhuang <yisen.zhuang@huawei.com>
> Subject: please help backporting some patches to stable release 20.11.9
> 
> External email: Use caution opening links or attachments
> 
> 
> 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 20.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 20.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 2023/06/23.
> 
> You can find the a temporary work-in-progress branch of the coming 20.11.9
> 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 20.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 20.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 20.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---
> e97738919c  Chaoyong He      net/nfp: fix Tx descriptor free logic of NFD3
> c1f0cdae14  Dariusz Sosnowski net/mlx5: fix drop action attribute validation
> db42a84233  Dengdui Huang    app/testpmd: fix crash with invalid queue
> 0622428215  Jie Hai          net/hns3: fix missing FEC capability
> cd41a27154  Jie Hai          net/hns3: get FEC capability from firmware
> ad4d51d277  Rongwei Liu      net/mlx5: forbid duplicated tag index in pattern
> template
> 7ae50175c7  Saoirse O'Donovan test/crypto: fix return value for SNOW3G

Re: please help backporting some patches to stable release 20.11.9

[huangdengdui]

db42a84233  Dengdui Huang    app/testpmd: fix crash with invalid queue

no need to backport this patch, because it depend on multiple other patches,
in addition, this bug has little impact.

On 2023/6/15 9:38, 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 20.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 20.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 2023/06/23.
> 
> You can find the a temporary work-in-progress branch of the coming 20.11.9
> 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 20.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 20.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 20.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---
> e97738919c  Chaoyong He      net/nfp: fix Tx descriptor free logic of NFD3
> c1f0cdae14  Dariusz Sosnowski net/mlx5: fix drop action attribute validation
> db42a84233  Dengdui Huang    app/testpmd: fix crash with invalid queue
> 0622428215  Jie Hai          net/hns3: fix missing FEC capability
> cd41a27154  Jie Hai          net/hns3: get FEC capability from firmware
> ad4d51d277  Rongwei Liu      net/mlx5: forbid duplicated tag index in pattern template
> 7ae50175c7  Saoirse O'Donovan test/crypto: fix return value for SNOW3G