Linux kernel -stable discussions
 help / color / mirror / Atom feed
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, stable@vger.kernel.org,
	Vega <vega@nebusec.ai>
Subject: Re: [PATCH net v2 1/1] net: l2tp: do not propagate multicast notification errors
Date: Mon, 24 Aug 2026 12:21:11 +0100	[thread overview]
Message-ID: <20260824112111.GQ265046@horms.kernel.org> (raw)
In-Reply-To: <54f48e812ca0424c47ffdb9a8182180921f7e6b2.1787247008.git.zihanx@nebusec.ai>

On Thu, Aug 20, 2026 at 06:40:28PM +0000, Zihan Xi wrote:
> The tunnel create, tunnel modify, session create, and session modify
> netlink handlers send multicast notifications through helpers that can fail
> while allocating or encoding a message, or while multicasting it.
> 
> For tunnel and session create/modify, a notification is sent after the live
> operation has completed. Returning a best-effort notification error as the
> command result can therefore report failure for an operation that already
> committed and can cause callers to retry and accumulate live objects.
> 
> Keep sending notifications for listener visibility, but do not propagate
> their best-effort status as the command result. This also keeps the tunnel
> modify command consistent with the other notification-only paths.
> 
> 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>
> ---
> changes in v2:
>   - Extend best-effort notification handling to tunnel_modify.
>   - Follow the existing bare-call style instead of explicit (void) casts.
>   - Document the observed ENOBUFS and committed-state reproduction.
>   - v1 Link: https://lore.kernel.org/all/cover.1786962220.git.zihanx@nebusec.ai/

Thanks for the updates.

Reviewed-by: Simon Horman <horms@kernel.org>


      reply	other threads:[~2026-08-24 11:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1787247008.git.zihanx@nebusec.ai>
2026-08-20 18:40 ` [PATCH net v2 1/1] net: l2tp: do not propagate multicast notification errors Zihan Xi
2026-08-24 11:21   ` 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=20260824112111.GQ265046@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --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