From: Jakub Kicinski <kuba@kernel.org>
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [net-next,v4,05/13] octeontx2-af: npc: cn20k: Allocate default MCAM indexes
Date: Mon, 19 Jan 2026 09:32:45 -0800 [thread overview]
Message-ID: <20260119093245.0544f5ce@kernel.org> (raw)
In-Reply-To: <aW2oKKg73zwRNals@rkannoth-OptiPlex-7090>
On Mon, 19 Jan 2026 09:12:32 +0530 Ratheesh Kannoth wrote:
> > > - if (attach->nixlf)
> > > + if (attach->nixlf) {
> > > rvu_attach_block(rvu, pcifunc, BLKTYPE_NIX, 1, attach);
> > > + if (is_cn20k(rvu->pdev)) {
> > > + err = npc_cn20k_dft_rules_alloc(rvu, pcifunc);
> > > + if (err)
> > > + goto exit;
> > ^^^^
> >
> > When npc_cn20k_dft_rules_alloc() fails after rvu_attach_block() has
> > already attached the NIX LF, the error path jumps to exit without
> > detaching NIX. The caller (otx2_init_rsrc in otx2_pf.c) assumes that on
> > error nothing was attached, so it does not call otx2_detach_resources().
> >
> > Could this leave NIX LF attached without proper cleanup on allocation
> > failure?
> There is no proper error handling done for rvu_attach_block function (in existing code)
> We can address this later as different patch ?
Different patch, yes, but _before_ these patches are merged.
next prev parent reply other threads:[~2026-01-19 17:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 10:16 [PATCH net-next v4 00/13] NPC HW block support for cn20k Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 01/13] octeontx2-af: npc: cn20k: Index management Ratheesh Kannoth
2026-01-18 0:39 ` Jakub Kicinski
2026-01-19 4:04 ` Ratheesh Kannoth
2026-01-18 0:40 ` [net-next,v4,01/13] " Jakub Kicinski
2026-01-19 4:00 ` Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 02/13] octeontx2-af: npc: cn20k: KPM profile changes Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 03/13] octeontx2-af: npc: cn20k: Add default profile Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 04/13] ocetontx2-af: npc: cn20k: MKEX profile support Ratheesh Kannoth
2026-01-18 0:40 ` [net-next,v4,04/13] " Jakub Kicinski
2026-01-19 4:17 ` Ratheesh Kannoth
2026-01-20 3:24 ` Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 05/13] octeontx2-af: npc: cn20k: Allocate default MCAM indexes Ratheesh Kannoth
2026-01-18 0:40 ` [net-next,v4,05/13] " Jakub Kicinski
2026-01-19 3:42 ` Ratheesh Kannoth
2026-01-19 17:32 ` Jakub Kicinski [this message]
2026-01-20 1:37 ` Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 06/13] octeontx2-af: npc: cn20k: Use common APIs Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 07/13] octeontx2-af: npc: cn20k: Prepare for new SoC Ratheesh Kannoth
2026-01-22 8:36 ` Simon Horman
2026-01-23 15:39 ` Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 08/13] octeontx2-af: npc: cn20k: Add new mailboxes for CN20K silicon Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 09/13] octeontx2-af: npc: cn20k: virtual index support Ratheesh Kannoth
2026-01-18 0:40 ` [net-next,v4,09/13] " Jakub Kicinski
2026-01-19 3:39 ` Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 10/13] octeontx2-af: npc: cn20k: Allocate MCAM entry for flow installation Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 11/13] octeontx2-pf: cn20k: Add TC rules support Ratheesh Kannoth
2026-01-18 0:40 ` [net-next,v4,11/13] " Jakub Kicinski
2026-01-19 3:39 ` Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 12/13] octeontx2-af: npc: cn20k: add debugfs support Ratheesh Kannoth
2026-01-13 10:16 ` [PATCH net-next v4 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=20260119093245.0544f5ce@kernel.org \
--to=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rkannoth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.