please help backporting some patches to stable release 20.11.7

please help backporting some patches to stable release 20.11.7

[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 2022/11/24.

You can find the a temporary work-in-progress branch of the coming 20.11.7
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 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

---
63bd264485  Frank Du         net/ice: fix interrupt handler unregister
beaf1f876c  Hernan Vargas    baseband/acc: fix double MSI interrupt in TB mode
3e13a6ae95  Jiawei Wang      net/mlx5: fix mirror flow validation with ASO action
e9de8f33ca  Jiawei Wang      net/mlx5: fix source port checking in sample flow rule
afb98009a0  Shun Hao         net/mlx5: fix assert when creating meter policy

Re: please help backporting some patches to stable release 20.11.7

[lihuisong (C)]

在 2022/11/8 18:25, Luca Boccassi 写道:
> On Tue, 8 Nov 2022 at 02:01, lihuisong (C) <lihuisong@huawei.com> wrote:
>> Hi Luca Boccassi,
>>
>> It seems that queued patches are not merged into 20.11.7 branch.
>> These patches in this backporting list are hard to backport.
>> Is there any other code branch?
>>
>> Regards,
>> Huisong
> Yes, it is linked in the email
Ok. thanks, Luca Boccassi
>
>> 在 2022/11/3 17:40, luca.boccassi@gmail.com 写道:
>>> 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 11/10/22.
>>>
>>> You can find the a temporary work-in-progress branch of the coming 20.11.7
>>> 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
>>>
>>> ---
>>> 8ae946970e  Abdullah Ömer Yamaç eal: fix thread name for high order lcores
>>> 09b5b2880d  Benjamin Le Berre net/bnxt: fix error code during MTU change
>>> b38bd88beb  Huisong Li       net/hns3: fix clearing hardware MAC statistics
>>> 0d81da2559  Huisong Li       net/hns3: fix RSS rule restore
>>> 8f81056e5a  Qi Zhang         net/ice/base: fix 100M speed capability
>>> 04ab2b2f0b  Qi Zhang         net/ice/base: fix comment of overloaded GCO bit
>>> 40ff47dd4b  Qi Zhang         net/ice/base: fix double VLAN in promiscuous mode
>>> b0472e210f  Qi Zhang         net/ice/base: fix input set of GTPoGRE
>>> 38ef9e1b99  Qi Zhang         net/ice/base: fix null pointer dereference
>>> 27b7bdae1d  Qi Zhang         net/ice: fix DDP package init
>>> 3b8c645afa  Zhichao Zeng     net/iavf: fix outer checksum flags
>>> 1aaacea174  Zhichao Zeng     net/iavf: fix processing VLAN TCI in SSE path
>>>
>>> .
> .

Re: please help backporting some patches to stable release 20.11.7

[Luca Boccassi]

On Tue, 8 Nov 2022 at 02:01, lihuisong (C) <lihuisong@huawei.com> wrote:
>
> Hi Luca Boccassi,
>
> It seems that queued patches are not merged into 20.11.7 branch.
> These patches in this backporting list are hard to backport.
> Is there any other code branch?
>
> Regards,
> Huisong

Yes, it is linked in the email

> 在 2022/11/3 17:40, luca.boccassi@gmail.com 写道:
> > 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 11/10/22.
> >
> > You can find the a temporary work-in-progress branch of the coming 20.11.7
> > 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
> >
> > ---
> > 8ae946970e  Abdullah Ömer Yamaç eal: fix thread name for high order lcores
> > 09b5b2880d  Benjamin Le Berre net/bnxt: fix error code during MTU change
> > b38bd88beb  Huisong Li       net/hns3: fix clearing hardware MAC statistics
> > 0d81da2559  Huisong Li       net/hns3: fix RSS rule restore
> > 8f81056e5a  Qi Zhang         net/ice/base: fix 100M speed capability
> > 04ab2b2f0b  Qi Zhang         net/ice/base: fix comment of overloaded GCO bit
> > 40ff47dd4b  Qi Zhang         net/ice/base: fix double VLAN in promiscuous mode
> > b0472e210f  Qi Zhang         net/ice/base: fix input set of GTPoGRE
> > 38ef9e1b99  Qi Zhang         net/ice/base: fix null pointer dereference
> > 27b7bdae1d  Qi Zhang         net/ice: fix DDP package init
> > 3b8c645afa  Zhichao Zeng     net/iavf: fix outer checksum flags
> > 1aaacea174  Zhichao Zeng     net/iavf: fix processing VLAN TCI in SSE path
> >
> > .

Re: please help backporting some patches to stable release 20.11.7

[lihuisong (C)]

Hi Luca Boccassi,

It seems that queued patches are not merged into 20.11.7 branch.
These patches in this backporting list are hard to backport.
Is there any other code branch?

Regards,
Huisong

在 2022/11/3 17:40, luca.boccassi@gmail.com 写道:
> 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 11/10/22.
>
> You can find the a temporary work-in-progress branch of the coming 20.11.7
> 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
>
> ---
> 8ae946970e  Abdullah Ömer Yamaç eal: fix thread name for high order lcores
> 09b5b2880d  Benjamin Le Berre net/bnxt: fix error code during MTU change
> b38bd88beb  Huisong Li       net/hns3: fix clearing hardware MAC statistics
> 0d81da2559  Huisong Li       net/hns3: fix RSS rule restore
> 8f81056e5a  Qi Zhang         net/ice/base: fix 100M speed capability
> 04ab2b2f0b  Qi Zhang         net/ice/base: fix comment of overloaded GCO bit
> 40ff47dd4b  Qi Zhang         net/ice/base: fix double VLAN in promiscuous mode
> b0472e210f  Qi Zhang         net/ice/base: fix input set of GTPoGRE
> 38ef9e1b99  Qi Zhang         net/ice/base: fix null pointer dereference
> 27b7bdae1d  Qi Zhang         net/ice: fix DDP package init
> 3b8c645afa  Zhichao Zeng     net/iavf: fix outer checksum flags
> 1aaacea174  Zhichao Zeng     net/iavf: fix processing VLAN TCI in SSE path
>
> .

please help backporting some patches to stable release 20.11.7

[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 11/12/22.

You can find the a temporary work-in-progress branch of the coming 20.11.7
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

---
2df5fe2023  Hernan Vargas    baseband/acc100: check AQ availability
5802f36dd4  Hernan Vargas    baseband/acc100: enforce additional check on FCW
75114f78cf  Hernan Vargas    baseband/acc100: fix null HARQ input case
c24d53b4cc  Hernan Vargas    baseband/acc100: fix ring availability calculation
459531c958  Morten Brørup    mempool: fix cache flushing algorithm
927cb43fe9  Pavan Nikhilesh  examples/l3fwd: fix port group mask with AltiVec
dbad6f64f9  Peng Zhang       net/nfp: fix internal buffer size and MTU check

Re: please help backporting some patches to stable release 20.11.7

[Benjamin Le Berre]

Hi,

I don't think that 09b5b2880d ("net/bnxt: fix error code during MTU
change") is meant to be backported to 20.11 since it is a fix to
a42ab1eb33ff ("net/bnxt: disallow MTU change when device is started")
which seems to not have been backported, although I cannot find
confirmation that it should have been skipped for the 20.11.6 release.

Kind Regards,
Benjamin Le Berre.

On Thu, Nov 3, 2022 at 10:41 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 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 11/10/22.
>
> You can find the a temporary work-in-progress branch of the coming 20.11.7
> 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
>
> ---
> 8ae946970e  Abdullah Ömer Yamaç eal: fix thread name for high order lcores
> 09b5b2880d  Benjamin Le Berre net/bnxt: fix error code during MTU change
> b38bd88beb  Huisong Li       net/hns3: fix clearing hardware MAC statistics
> 0d81da2559  Huisong Li       net/hns3: fix RSS rule restore
> 8f81056e5a  Qi Zhang         net/ice/base: fix 100M speed capability
> 04ab2b2f0b  Qi Zhang         net/ice/base: fix comment of overloaded GCO bit
> 40ff47dd4b  Qi Zhang         net/ice/base: fix double VLAN in promiscuous mode
> b0472e210f  Qi Zhang         net/ice/base: fix input set of GTPoGRE
> 38ef9e1b99  Qi Zhang         net/ice/base: fix null pointer dereference
> 27b7bdae1d  Qi Zhang         net/ice: fix DDP package init
> 3b8c645afa  Zhichao Zeng     net/iavf: fix outer checksum flags
> 1aaacea174  Zhichao Zeng     net/iavf: fix processing VLAN TCI in SSE path

please help backporting some patches to stable release 20.11.7

[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 11/10/22.

You can find the a temporary work-in-progress branch of the coming 20.11.7
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

---
8ae946970e  Abdullah Ömer Yamaç eal: fix thread name for high order lcores
09b5b2880d  Benjamin Le Berre net/bnxt: fix error code during MTU change
b38bd88beb  Huisong Li       net/hns3: fix clearing hardware MAC statistics
0d81da2559  Huisong Li       net/hns3: fix RSS rule restore
8f81056e5a  Qi Zhang         net/ice/base: fix 100M speed capability
04ab2b2f0b  Qi Zhang         net/ice/base: fix comment of overloaded GCO bit
40ff47dd4b  Qi Zhang         net/ice/base: fix double VLAN in promiscuous mode
b0472e210f  Qi Zhang         net/ice/base: fix input set of GTPoGRE
38ef9e1b99  Qi Zhang         net/ice/base: fix null pointer dereference
27b7bdae1d  Qi Zhang         net/ice: fix DDP package init
3b8c645afa  Zhichao Zeng     net/iavf: fix outer checksum flags
1aaacea174  Zhichao Zeng     net/iavf: fix processing VLAN TCI in SSE path