From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: cedric.jehasse@luminex.be, netdev@vger.kernel.org,
olteanv@gmail.com, edumazet@google.com, davem@davemloft.net,
pabeni@redhat.com, linux@armlinux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [net-next,v4] net: dsa: mv88e6xxx: Add partial support for TCAM entries
Date: Fri, 27 Feb 2026 15:55:46 -0800 [thread overview]
Message-ID: <20260227155546.6f861f76@kernel.org> (raw)
In-Reply-To: <f6885957-998c-4793-93a0-d3cf957ba702@lunn.ch>
On Fri, 27 Feb 2026 15:06:35 +0100 Andrew Lunn wrote:
> > If entry_add() fails after some entries have already been moved to new
> > hardware positions with their hw_idx updated, doesn't the function return
> > without rolling back those partial moves?
> >
> > The software list would then have some entries pointing to their new
> > positions while the gap for the new entry is only partially created.
> > This could leave the TCAM in an inconsistent state for subsequent
> > operations.
> >
> > Is there error handling to ensure the TCAM state remains consistent when
> > insertion partially succeeds?
>
> Can we get replies to previous versions of the patch series included
> into the context that the AI is using to perform reviews? This has
> been explained once as being safe.
It should fetch the mailing list threads from previous postings.
but it's a bit in flux because sometimes it sends too much $$ doing
that. And other times it causes too many false positives.
prev parent reply other threads:[~2026-02-27 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 13:37 [PATCH net-next v4] net: dsa: mv88e6xxx: Add partial support for TCAM entries Cedric Jehasse via B4 Relay
2026-02-27 3:55 ` [net-next,v4] " Jakub Kicinski
2026-02-27 9:44 ` Cedric Jehasse
2026-02-28 1:28 ` Jakub Kicinski
2026-03-02 13:36 ` Cedric Jehasse
2026-03-03 0:13 ` Jakub Kicinski
2026-02-27 14:06 ` Andrew Lunn
2026-02-27 23:55 ` Jakub Kicinski [this message]
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=20260227155546.6f861f76@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=cedric.jehasse@luminex.be \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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