Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Julius Bairaktaris" <julius@bairaktaris.de>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH nf-next v3 2/3] netfilter: flowtable: carry a priority into the offload
Date: Mon, 05 Oct 2026 17:16:47 +0000	[thread overview]
Message-ID: <20261005171647.CCCB51F0089B@smtp.kernel.org> (raw)
In-Reply-To: <20261004171636.3545085-3-julius@bairaktaris.de>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] tc: mtk_ppe: silently ignores FLOW_ACTION_PRIORITY for TC flower offload
--

commit a587674714a18a7d90f4418de25fb5ffa3691fa3
Author: Julius Bairaktaris <julius@bairaktaris.de>

netfilter: flowtable: carry a priority into the offload

This commit updates the flowtable to store the skb->priority of the packet
that creates the flow, and emit it as FLOW_ACTION_PRIORITY during offload.
It also updates the airoha and mtk drivers to parse this action in their
shared flowtable and TC flower offload functions.

> diff --git a/drivers/net/ethernet/mediatek/mtk_ppe_offload.c b/drivers/net/ethernet/mediatek/mtk_ppe_offload.c
> index 99b28aaa7cc47..4ee99e8e4a34b 100644
> --- a/drivers/net/ethernet/mediatek/mtk_ppe_offload.c
> +++ b/drivers/net/ethernet/mediatek/mtk_ppe_offload.c

[ ... ]

> @@ -378,6 +378,7 @@ mtk_flow_offload_replace(struct mtk_eth *eth, struct flow_cls_offload *f,
>  		case FLOW_ACTION_REDIRECT:
>  			odev = act->dev;
>  			break;
> +		case FLOW_ACTION_PRIORITY:
>  		case FLOW_ACTION_CSUM:
>  			break;

[Severity: Medium]
Does this silently ignore explicit QoS queuing requests from TC flower?

Because mtk_flow_offload_replace() is shared for both netfilter flowtable
and TC flower offloads, accommodating flowtable packets by returning success
here causes the driver to also accept and silently discard "skbedit priority"
actions from TC rules. 

Hardware will silently drop the explicit QoS queuing request instead of
returning -EOPNOTSUPP, causing traffic to use default queues instead of
the requested priority queue without warning the user.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261004171636.3545085-1-julius@bairaktaris.de?part=2

  reply	other threads:[~2026-10-05 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 17:16 [PATCH nf-next v3 0/3] netfilter: flowtable: carry a priority into the offload Julius Bairaktaris
2026-10-04 17:16 ` [PATCH nf-next v3 1/3] net/mlx5e: Ignore FLOW_ACTION_PRIORITY on flowtable offload Julius Bairaktaris
2026-10-05 17:16   ` sashiko-bot
2026-10-04 17:16 ` [PATCH nf-next v3 2/3] netfilter: flowtable: carry a priority into the offload Julius Bairaktaris
2026-10-05 17:16   ` sashiko-bot [this message]
2026-10-04 17:16 ` [PATCH nf-next v3 3/3] selftests: netfilter: nft_flowtable.sh: check the priority a flow carries Julius Bairaktaris
2026-10-05 17:16   ` sashiko-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261005171647.CCCB51F0089B@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=julius@bairaktaris.de \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox