From: Oleg Nesterov <oleg@redhat.com>
To: Nam Cao <namcao@linutronix.de>
Cc: Shuah Khan <shuah@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dylan Hatch <dylanbhatch@google.com>,
"Eric W . Biederman" <ebiederm@xmission.com>,
John Ogness <john.ogness@linutronix.de>,
Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kselftest@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] fs/proc: do_task_stat: Fix ESP not readable during coredump
Date: Tue, 17 Dec 2024 15:59:52 +0100 [thread overview]
Message-ID: <20241217145923.GA29091@redhat.com> (raw)
In-Reply-To: <11e1777296b7d06085c9fd341bafc4b9d82e6e4e.1730883229.git.namcao@linutronix.de>
On 11/06, Nam Cao wrote:
>
> @@ -534,6 +517,23 @@ static int do_task_stat(struct seq_file *m, struct pid_namespace *ns,
> ppid = task_tgid_nr_ns(task->real_parent, ns);
> pgid = task_pgrp_nr_ns(task, ns);
>
> + /*
> + * esp and eip are intentionally zeroed out. There is no
> + * non-racy way to read them without freezing the task.
> + * Programs that need reliable values can use ptrace(2).
OK,
but then:
> + * The only exception is if the task is core dumping because
> + * a program is not able to use ptrace(2) in that case. It is
> + * safe because the task has stopped executing permanently.
> + */
> + if (permitted && task->signal->core_state) {
> + if (try_get_task_stack(task)) {
> + eip = KSTK_EIP(task);
> + esp = KSTK_ESP(task);
> + put_task_stack(task);
How can the task->signal->core_state check help ?
Suppose we have a task T1 with T1-pid == 100 and you read /proc/100/stat.
It is possible that the T1's sub-thread T2 starts the coredumping and sets
signal->core_state != NULL.
But read(/proc/100/stat) can run before T1 gets SIGKILL from T2 and enters
the kernel mode?
Oleg.
next prev parent reply other threads:[~2024-12-17 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1730883229.git.namcao@linutronix.de>
2024-11-06 9:22 ` [PATCH 1/2] fs/proc: do_task_stat: Fix ESP not readable during coredump Nam Cao
2024-11-06 14:30 ` John Ogness
2024-12-17 12:50 ` Thomas Gleixner
2024-12-17 14:59 ` Oleg Nesterov [this message]
2024-12-17 15:09 ` Oleg Nesterov
2024-12-20 14:53 ` Nam Cao
2024-12-22 19:18 ` Oleg Nesterov
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=20241217145923.GA29091@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dylanbhatch@google.com \
--cc=ebiederm@xmission.com \
--cc=john.ogness@linutronix.de \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=shuah@kernel.org \
--cc=stable@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