From: Simon Horman <horms@kernel.org>
To: Zihan Xi <zihanx@nebusec.ai>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, bhong@brocade.com,
stephen@networkplumber.org, sven@brocade.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Vega <vega@nebusec.ai>
Subject: Re: [PATCH net 1/1] net: l2tp: ignore multicast notification errors in netlink commands
Date: Thu, 20 Aug 2026 16:28:02 +0100 [thread overview]
Message-ID: <20260820152802.GZ265046@horms.kernel.org> (raw)
In-Reply-To: <e9cf566687c906ba6843f72b28f11a3431a595b5.1786962220.git.zihanx@nebusec.ai>
On Mon, Aug 17, 2026 at 05:21:09PM +0000, Zihan Xi wrote:
> l2tp_nl_cmd_tunnel_create(), l2tp_nl_cmd_session_create(), and
> l2tp_nl_cmd_session_modify() update live state before sending their
> multicast notifications. A notification helper can fail while allocating
> or encoding the message, or while multicasting it. Returning any such
> best-effort notification error after the state change makes a successful
> command look like a failure and can cause retries to accumulate live
> objects.
Is this a theoretical problem, or something that has been observed?
> Keep sending notifications for listener visibility, but do not let their
> best-effort status overwrite the command result. The explicit (void) casts
> make this intentional for all notification helper failures.
I don't think the (void) cast is in keeping with the existing code
in this file.
> Fixes: 33f72e6f0c67 ("l2tp : multicast notification to the registered listeners")
> Cc: stable@vger.kernel.org
> Reported-by: Vega <vega@nebusec.ai>
> Assisted-by: Codex:gpt-5.4
> Signed-off-by: Zihan Xi <zihanx@nebusec.ai>
I am wondering if you considered extending this patch to
also cover l2tp_nl_cmd_tunnel_modify().
...
prev parent reply other threads:[~2026-08-20 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 16:53 [PATCH net 0/1] net: l2tp: ignore multicast notification errors in netlink commands Zihan Xi
2026-08-17 17:21 ` [PATCH net 1/1] " Zihan Xi
2026-08-17 17:21 ` Zihan Xi
2026-08-20 15:28 ` Simon Horman [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=20260820152802.GZ265046@horms.kernel.org \
--to=horms@kernel.org \
--cc=bhong@brocade.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=sven@brocade.com \
--cc=vega@nebusec.ai \
--cc=zihanx@nebusec.ai \
/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