Linux Documentation
 help / color / mirror / Atom feed
From: Qingfang Deng <qingfang.deng@linux.dev>
To: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Breno Leitao <leitao@debian.org>,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Paul Mackerras <paulus@ozlabs.org>
Subject: Re: [PATCH net-next] ppp: update channel locking comment and doc
Date: Mon, 10 Aug 2026 09:19:28 +0800	[thread overview]
Message-ID: <01f94272-da18-4a6f-8907-c482522a8ae6@linux.dev> (raw)
In-Reply-To: <20260807060153.1380548-1-qingfang.deng@linux.dev>

On 2026/8/7 14:01, Qingfang Deng wrote:
> Commit ec4215683e47 ("ppp: defer channel free to an RCU grace period to
> fix pppol2tp RX UAF") defers freeing generic channel state to an RCU
> grace period via call_rcu().
>
> Update the SMP locking notes comment in include/linux/ppp_channel.h and
> Documentation/networking/ppp_generic.rst to reflect that in-flight RCU
> readers can complete safely after ppp_unregister_channel().
>
> Reported by Sashiko.
>
> Signed-off-by: Qingfang Deng <qingfang.deng@linux.dev>


Sashiko pointed out more issues. I should keep the comments for now.

---
pw-bot: cr


      reply	other threads:[~2026-08-10  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  6:01 [PATCH net-next] ppp: update channel locking comment and doc Qingfang Deng
2026-08-10  1:19 ` Qingfang Deng [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=01f94272-da18-4a6f-8907-c482522a8ae6@linux.dev \
    --to=qingfang.deng@linux.dev \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paulus@ozlabs.org \
    --cc=skhan@linuxfoundation.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