From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Petr Pavlu <petr.pavlu@suse.com>,
Qingfang Deng <qingfang.deng@linux.dev>,
Breno Leitao <leitao@debian.org>,
Norbert Szetei <norbert@doyensec.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Taegu Ha <hataegu0826@gmail.com>, Kees Cook <kees@kernel.org>,
linux-ppp@vger.kernel.org, linux-kernel@vger.kernel.org,
Guillaume Nault <gnault@redhat.com>,
netdev@vger.kernel.org, Luis Chamberlain <mcgrof@kernel.org>,
Daniel Gomez <da.gomez@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Aaron Tomlin <atomlin@atomlin.com>,
linux-modules@vger.kernel.org
Subject: Re: [PATCH net v2] ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF
Date: Wed, 8 Jul 2026 11:11:47 +0200 [thread overview]
Message-ID: <20260708091147.O1d41Vi0@linutronix.de> (raw)
In-Reply-To: <7ff3af97-1c10-4f46-84ae-ffbf757f7e9e@paulmck-laptop>
On 2026-07-07 09:39:01 [-0700], Paul E. McKenney wrote:
> Alternatives include:
>
> o Provide a patch like that above, but only execute the
> rcu_barrier() in some debug mode. If your code works when
> that debug is enabled but does not otherwise, you add the
> rcu_barrier().
>
> o If debug is enabled, make rcu_do_batch() check the function
> before invoking it. If the function is not mapped, issue a
> diagnostic, and don't try to invoke the function. (But is
> there a sufficiently cheap way to check for the function not
> being mapped?)
In both cases you would see a backtrace and the name of the last
unloaded module. And since we don't see a lot of these reports, people
either don't run into this because it does not exist or RCU is quick
enough.
>
> Thanx, Paul
Sebastian
next prev parent reply other threads:[~2026-07-08 9:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 18:12 [PATCH net v2] ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF Norbert Szetei
2026-07-02 8:19 ` Qingfang Deng
2026-07-03 16:05 ` Guillaume Nault
2026-07-03 7:27 ` Qingfang Deng
2026-07-03 16:32 ` Breno Leitao
2026-07-05 2:57 ` Qingfang Deng
2026-07-06 9:29 ` Sebastian Andrzej Siewior
2026-07-07 15:32 ` Petr Pavlu
2026-07-07 16:39 ` Paul E. McKenney
2026-07-08 9:11 ` Sebastian Andrzej Siewior [this message]
2026-07-08 14:01 ` Paul E. McKenney
2026-07-08 7:49 ` Sebastian Andrzej Siewior
2026-07-08 13:04 ` Petr Pavlu
2026-07-08 13:56 ` Sebastian Andrzej Siewior
2026-07-08 19:00 ` Sebastian Andrzej Siewior
2026-07-08 19:22 ` Paul E. McKenney
2026-07-14 16:01 ` Sebastian Andrzej Siewior
2026-07-14 17:47 ` Paul E. McKenney
2026-07-06 7:22 ` Norbert Szetei
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=20260708091147.O1d41Vi0@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andrew+netdev@lunn.ch \
--cc=atomlin@atomlin.com \
--cc=da.gomez@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=hataegu0826@gmail.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=norbert@doyensec.com \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=qingfang.deng@linux.dev \
--cc=samitolvanen@google.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.