From: Oleg Nesterov <oleg@redhat.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org,
Linux Containers <containers@lists.linux-foundation.org>,
Christof Meerwald <cmeerw@cmeerw.org>
Subject: Re: [PATCH] signal: Avoid corrupting si_pid and si_uid in do_notify_parent
Date: Tue, 21 Apr 2020 13:28:31 +0200 [thread overview]
Message-ID: <20200421112831.GD6787@redhat.com> (raw)
In-Reply-To: <20200421111139.GC6787@redhat.com>
On 04/21, Oleg Nesterov wrote:
>
> The corner case is release_task() when the last exiting sub-thread sends
> a signal on behalf of its ->group_leader, and at this point all the tsk's
> pid pointers are NULL, that is why "force" can be falsely "true".
Or do_notify_parent() can be called by debugger from the parent namespace,
in this case "force" can be falsely "true" too.
Oleg.
next prev parent reply other threads:[~2020-04-21 11:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 20:13 SIGCHLD signal sometimes sent with si_pid==0 (Linux 5.6.5) Christof Meerwald
2020-04-20 17:05 ` [PATCH] signal: Avoid corrupting si_pid and si_uid in do_notify_parent Eric W. Biederman
2020-04-21 8:30 ` Christian Brauner
2020-04-21 9:28 ` Oleg Nesterov
2020-04-21 10:21 ` Christian Brauner
2020-04-21 11:11 ` Oleg Nesterov
2020-04-21 11:26 ` Christian Brauner
2020-04-21 12:17 ` Oleg Nesterov
2020-04-21 12:59 ` Christian Brauner
2020-04-21 13:42 ` Eric W. Biederman
2020-04-21 11:28 ` Oleg Nesterov [this message]
2020-04-21 11:38 ` Christian Brauner
2020-04-21 10:28 ` Christian Brauner
2020-04-21 14:57 ` Eric W. Biederman
2020-04-21 15:08 ` Christian Brauner
2020-04-21 9:04 ` Oleg Nesterov
2020-04-21 10:19 ` [PATCH] remove the no longer needed pid_alive() check in __task_pid_nr_ns() Oleg Nesterov
2020-04-21 10:50 ` Christian Brauner
2020-04-21 15:05 ` Eric W. Biederman
2020-04-24 18:05 ` Oleg Nesterov
2020-04-24 19:54 ` Eric W. Biederman
2020-04-21 14:59 ` SIGCHLD signal sometimes sent with si_pid==0 (Linux 5.6.5) Eric W. Biederman
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=20200421112831.GD6787@redhat.com \
--to=oleg@redhat.com \
--cc=christian.brauner@ubuntu.com \
--cc=cmeerw@cmeerw.org \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@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 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.