From: Ratheesh Kannoth <rkannoth@marvell.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [net-next,v7,09/13] octeontx2-af: npc: cn20k: virtual index support
Date: Mon, 2 Feb 2026 09:41:06 +0530 [thread overview]
Message-ID: <aYAj2gIfrlNq2_zt@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <20260131033322.1013834-1-kuba@kernel.org>
On 2026-01-31 at 09:03:22, Jakub Kicinski (kuba@kernel.org) wrote:
>
> > +fail1:
> > + if (xa_insert(&npc_priv.xa_idx2vidx_map, old_midx,
> > + xa_mk_value(vidx), GFP_KERNEL))
> > + dev_err(rvu->dev,
> > + "%s: Faled to roll back vidx2idx to old_midx=%u, vidx=%u\n",
> > + __func__, old_midx, vidx);
> > +
> > + return rc;
> > +}
>
> When we jump to fail1, it's because the xa_insert() into xa_vidx2idx_map
> failed (around line 352). At that point, xa_idx2vidx_map hasn't been touched
> yet - only xa_vidx2idx_map had the vidx erased. The rollback here tries to
> insert into xa_idx2vidx_map, but shouldn't this restore vidx -> old_midx
> in xa_vidx2idx_map instead? This appears to be operating on the wrong xarray
> and would leave the mapping inconsistent on error.
>
> This was also raised in lore review feedback:
> https://lore.kernel.org/all/20260129051307.376632-1-kuba@kernel.org/
Label fall1: is modifying vidx2idx_map in V7. Am i missing anything here ?
next prev parent reply other threads:[~2026-02-02 4:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 8:33 [PATCH net-next v7 00/13] NPC HW block support for cn20k Ratheesh Kannoth
2026-01-29 8:33 ` [PATCH net-next v7 01/13] octeontx2-af: npc: cn20k: Index management Ratheesh Kannoth
2026-01-31 3:33 ` [net-next,v7,01/13] " Jakub Kicinski
2026-01-29 8:33 ` [PATCH net-next v7 02/13] octeontx2-af: npc: cn20k: KPM profile changes Ratheesh Kannoth
2026-01-29 8:33 ` [PATCH net-next v7 03/13] octeontx2-af: npc: cn20k: Add default profile Ratheesh Kannoth
2026-01-29 8:33 ` [PATCH net-next v7 04/13] octeontx2-af: npc: cn20k: MKEX profile support Ratheesh Kannoth
2026-01-29 8:33 ` [PATCH net-next v7 05/13] octeontx2-af: npc: cn20k: Allocate default MCAM indexes Ratheesh Kannoth
2026-01-29 8:33 ` [PATCH net-next v7 06/13] octeontx2-af: npc: cn20k: Use common APIs Ratheesh Kannoth
2026-01-29 8:33 ` [PATCH net-next v7 07/13] octeontx2-af: npc: cn20k: Prepare for new SoC Ratheesh Kannoth
2026-01-29 8:33 ` [PATCH net-next v7 08/13] octeontx2-af: npc: cn20k: Add new mailboxes for CN20K silicon Ratheesh Kannoth
2026-01-29 8:33 ` [PATCH net-next v7 09/13] octeontx2-af: npc: cn20k: virtual index support Ratheesh Kannoth
2026-01-31 3:33 ` [net-next,v7,09/13] " Jakub Kicinski
2026-02-02 4:11 ` Ratheesh Kannoth [this message]
2026-01-29 8:33 ` [PATCH net-next v7 10/13] octeontx2-af: npc: cn20k: Allocate MCAM entry for flow installation Ratheesh Kannoth
2026-01-29 8:33 ` [PATCH net-next v7 11/13] octeontx2-pf: cn20k: Add TC rules support Ratheesh Kannoth
2026-01-31 3:33 ` [net-next,v7,11/13] " Jakub Kicinski
2026-01-29 8:33 ` [PATCH net-next v7 12/13] octeontx2-af: npc: cn20k: add debugfs support Ratheesh Kannoth
2026-01-29 8:33 ` [PATCH net-next v7 13/13] octeontx2-af: npc: Use common structures 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=aYAj2gIfrlNq2_zt@rkannoth-OptiPlex-7090 \
--to=rkannoth@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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