From: "Paul E. McKenney" <paulmck@kernel.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Oleg Nesterov <oleg@redhat.com>,
Pengfei Xu <pengfei.xu@intel.com>,
Boqun Feng <boqun.feng@gmail.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
rcu@vger.kernel.org
Subject: Re: [PATCH 0/3] rcu-tasks: Fix race against exiting pid_ns
Date: Mon, 28 Nov 2022 16:22:40 -0800 [thread overview]
Message-ID: <20221129002240.GP4001@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20221125135500.1653800-1-frederic@kernel.org>
On Fri, Nov 25, 2022 at 02:54:57PM +0100, Frederic Weisbecker wrote:
> Pengfei Xu has reported a deadlock involving calls to unshare(),
> perf_event_open() and clone3() calls. It requires CAP_SYS_ADMIN
> to reproduce (at least I don't see a way for a non privilege process to
> reproduce).
>
> See this thread for details: https://lore.kernel.org/all/Y3sOgrOmMQqPMItu@xpf.sh.intel.com/
> And this document for the collaborative analysis with Boqun, Paul and Neeraj:
> https://docs.google.com/document/d/1hJxgiZ5TMZ4YJkdJPLAkRvq7sYQ-A7svgA8no6i-v8k
>
> The two first patches are small improvements. The fix is in the last patch.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> rcu/dev
>
> HEAD: 45ef5a0a4be4e0db9eadcc86e8f346d34c62e744
Hearing no objections, queued for further review and testing.
And thank you very much! That race between synchronize_rcu_tasks() and
zap_pid_ns_processes() certainly was more than a bit on the non-trivial
side. Good show!!!
Thanx, Paul
> Thanks,
> Frederic
> ---
>
> Frederic Weisbecker (3):
> rcu-tasks: Improve comments explaining tasks_rcu_exit_srcu purpose
> rcu-tasks: Remove preemption disablement around srcu_read_[un]lock() calls
> rcu-tasks: Fix synchronize_rcu_tasks() VS zap_pid_ns_processes()
>
>
> include/linux/rcupdate.h | 2 ++
> kernel/pid_namespace.c | 17 +++++++++++++++
> kernel/rcu/tasks.h | 55 ++++++++++++++++++++++++++++++++++++------------
> 3 files changed, 60 insertions(+), 14 deletions(-)
next prev parent reply other threads:[~2022-11-29 0:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 13:54 Frederic Weisbecker
2022-11-25 13:54 ` [PATCH 1/3] rcu-tasks: Improve comments explaining tasks_rcu_exit_srcu purpose Frederic Weisbecker
2022-11-25 13:54 ` [PATCH 2/3] rcu-tasks: Remove preemption disablement around srcu_read_[un]lock() calls Frederic Weisbecker
2022-11-25 13:55 ` [PATCH 3/3] rcu-tasks: Fix synchronize_rcu_tasks() VS zap_pid_ns_processes() Frederic Weisbecker
2022-11-30 18:37 ` Eric W. Biederman
2022-12-02 19:51 ` Paul E. McKenney
2022-12-02 22:54 ` Frederic Weisbecker
2022-12-02 23:28 ` Eric W. Biederman
2022-12-04 0:03 ` Frederic Weisbecker
2022-12-06 16:49 ` Oleg Nesterov
2022-12-07 14:34 ` Paul E. McKenney
2022-12-07 20:01 ` Frederic Weisbecker
2022-12-07 20:39 ` Oleg Nesterov
2022-12-09 20:26 ` Frederic Weisbecker
2022-11-29 0:22 ` Paul E. McKenney [this message]
2022-11-29 9:55 ` [PATCH 0/3] rcu-tasks: Fix race against exiting pid_ns Frederic Weisbecker
2022-11-29 14:48 ` Paul E. McKenney
2022-12-02 22:55 ` Frederic Weisbecker
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=20221129002240.GP4001@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=ebiederm@xmission.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pengfei.xu@intel.com \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.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
all inboxes | Powered by JetHome®