From: Ratheesh Kannoth <rkannoth@marvell.com>
To: <netdev-bot+sashiko@kernel.org>
Cc: <bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <andrew+netdev@lunn.ch>,
<ast@kernel.org>, <daniel@iogearbox.net>, <davem@davemloft.net>,
<edumazet@google.com>, <hawk@kernel.org>,
<john.fastabend@gmail.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <sdf@fomichev.me>, <sgoutham@marvell.com>
Subject: Re: [PATCH v18 net-next 1/2] octeontx2: use atomic bitops for PF/VF and rep flags
Date: Mon, 5 Oct 2026 09:46:12 +0530 [thread overview]
Message-ID: <asMkjGNqafk9xnC5@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <179092987490.434549.16075378413092077912@kernel.org>
On 2026-10-02 at 14:01:14, netdev-bot+sashiko@kernel.org (netdev-bot+sashiko@kernel.org) wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential
> issue(s) to consider.
>
> Critical: 0 · High: 1 (3) · Medium: 1 (5) · Low: 0
>
> If you believe none of the issues are legitimate, please reply to each
> issue of Medium severity or higher and explain why the AI is wrong.
> If any of them are legitimate and you plan to respin, please let patchwork
> know by including "pw-bot: cr" as a separate line at the end of your reply
> (one such reply per series is enough).
>
> - [High] otx2_sync_flags_from_rep() (otx2_common.h:625-634) updates the
> shared rep-PF flags word with a plain, non-atomic read-modify-write:…
> - [Medium] The patch quietly fixes a serious representor bug but gives it
> neither a Fixes: tag nor a description.
patch 1 is almost entirely mechanical (u64 masks → unsigned long + set_bit/clear_bit/test_bit)
It does not add new control flow. Reframed that way, every code issue Sashiko raised is a pre-existing defect
or race;
>
> Pre-existing issues:
> - [High] rvu_rep_destroy() (rep.c:637-643) calls free_netdev(rep->netdev)
> and then kfree(rep->flow_cfg).
> - [High] rep->stats_wrk is a delayed_work inside rep_dev, which is
> net_device private data.
> - [High] rvu_rep_mcam_flow_init() (rep.c:54-91) builds and sends NPC MCAM
> alloc mailbox messages (otx2_mbox_alloc_msg_npc_mcam_alloc_entry(),…
> - [Medium] otx2_tc_del_flow() (otx2_tc.c:1197-1198) clears
> OTX2_FLAG_TC_MARK_ENABLED on every delete of a mark flow, even when…
> - [Medium] rvu_rep_setup_tc_cb() (rep.c:115-121) ignores the return value
> of rvu_rep_mcam_flow_init() and then publishes rep->flow_cfg to…
> - [Medium] rvu_rep_mcam_flow_init() (rep.c:43-52) always overwrites
> rep->flow_cfg with a new kzalloc and never frees the previous one.
> - [Medium] rvu_rep_mcam_flow_init() allocates rep->flow_cfg with kzalloc
> and never calls refcount_set(&flow_cfg->mark_flows, 1).
> - [Medium] rvu_rep_state_evt_handler() (rep.c:297-309) uses the result of
> rvu_rep_get_repid() as an index into priv->reps[] without checking it,…
next prev parent reply other threads:[~2026-10-05 4:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 2:29 [PATCH v18 net-next 0/2] octeontx2: mqprio bandwidth offload for NIX TX schedulers Ratheesh Kannoth
2026-09-29 2:29 ` [PATCH v18 net-next 1/2] octeontx2: use atomic bitops for PF/VF and rep flags Ratheesh Kannoth
2026-10-02 8:31 ` netdev-bot+sashiko
2026-10-05 4:16 ` Ratheesh Kannoth [this message]
2026-09-29 2:29 ` [PATCH v18 net-next 2/2] octeontx2: add mqprio bandwidth offload for NIX TX schedulers Ratheesh Kannoth
2026-10-02 8:31 ` netdev-bot+sashiko
2026-10-02 1:22 ` [PATCH v18 net-next 0/2] octeontx2: " Jakub Kicinski
2026-10-02 9:37 ` David Laight
2026-10-05 2:58 ` Ratheesh Kannoth
2026-10-05 8:14 ` David Laight
2026-10-05 9:49 ` Ratheesh Kannoth
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=asMkjGNqafk9xnC5@rkannoth-OptiPlex-7090 \
--to=rkannoth@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=sgoutham@marvell.com \
/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