From: Oleg Nesterov <oleg@redhat.com>
To: alexjlzheng@gmail.com
Cc: usamaarif642@gmail.com, david@kernel.org,
akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
alexjlzheng@tencent.com, mingo@kernel.org, ruippan@tencent.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] procfs: fix missing RCU protection when reading real_parent in do_task_stat()
Date: Tue, 27 Jan 2026 18:25:25 +0100 [thread overview]
Message-ID: <aXj1BZY0P_NQp0yI@redhat.com> (raw)
In-Reply-To: <20260127150450.2073236-1-alexjlzheng@tencent.com>
On 01/27, alexjlzheng@gmail.com wrote:
>
> From: Jinliang Zheng <alexjlzheng@tencent.com>
>
> When reading /proc/[pid]/stat, do_task_stat() accesses task->real_parent
> without proper RCU protection, which leads:
Thanks for the patch...
> cpu 0 cpu 1
> ----- -----
> do_task_stat
> var = task->real_parent
> release_task
> call_rcu(delayed_put_task_struct)
> task_tgid_nr_ns(var)
> rcu_read_lock <--- Too late!
Almost off-topic, but I can't resist. This looks confusing to me.
It is not "Too late", this rcu_read_lock() protects another thing.
Nevermind.
I think that the changelog could be more clear. It should probably
mention that forget_original_parent() doesn't take child->signal->siglock
and thus we have a race... I dunno.
> --- a/fs/proc/array.c
> +++ b/fs/proc/array.c
> @@ -528,7 +528,9 @@ static int do_task_stat(struct seq_file *m, struct pid_namespace *ns,
> }
>
> sid = task_session_nr_ns(task, ns);
> - ppid = task_tgid_nr_ns(task->real_parent, ns);
> + rcu_read_lock();
> + ppid = task_tgid_nr_ns(rcu_dereference(task->real_parent), ns);
> + rcu_read_unlock();
But this can't really help. If task->real_parent has already exited and
it was reaped, then it is actually "Too late!" for rcu_read_lock().
Please use task_ppid_nr_ns() which does the necessary pid_alive() check.
Oleg.
next prev parent reply other threads:[~2026-01-27 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 15:04 [PATCH] procfs: fix missing RCU protection when reading real_parent in do_task_stat() alexjlzheng
2026-01-27 17:25 ` Oleg Nesterov [this message]
2026-01-27 18:49 ` Mateusz Guzik
2026-01-28 3:15 ` Jinliang Zheng
2026-01-28 8:01 ` Oleg Nesterov
2026-01-28 8:10 ` Jinliang Zheng
2026-01-28 3:10 ` Jinliang Zheng
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=aXj1BZY0P_NQp0yI@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexjlzheng@gmail.com \
--cc=alexjlzheng@tencent.com \
--cc=david@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mingo@kernel.org \
--cc=ruippan@tencent.com \
--cc=usamaarif642@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox