From: Oleg Nesterov <oleg@redhat.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Tycho Andersen <tycho@tycho.pizza>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pidfd: change do_notify_pidfd() to use __wake_up(poll_to_key(EPOLLIN))
Date: Mon, 5 Feb 2024 15:22:29 +0100 [thread overview]
Message-ID: <20240205142229.GA16757@redhat.com> (raw)
In-Reply-To: <20240205141050.GA16278@redhat.com>
Argh, sorry for noise Christian, I have sent the same patch twice.
Please ignore this email, the next email from me with the same
subject adds the reference to our discussion into the changelog.
On 02/05, Oleg Nesterov wrote:
>
> rather than wake_up_all(). This way do_notify_pidfd() won't wakeup the
> POLLHUP-only waiters which wait for pid_task() == NULL.
>
> TODO:
> - as Christian pointed out, this asks for the new wake_up_all_poll()
> helper, it can already have other users.
>
> - we can probably discriminate the PIDFD_THREAD and non-PIDFD_THREAD
> waiters, but this needs more work.
>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> ---
> kernel/signal.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/signal.c b/kernel/signal.c
> index 9b40109f0c56..c3fac06937e2 100644
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2021,11 +2021,12 @@ int send_sigqueue(struct sigqueue *q, struct pid *pid, enum pid_type type)
>
> void do_notify_pidfd(struct task_struct *task)
> {
> - struct pid *pid;
> + struct pid *pid = task_pid(task);
>
> WARN_ON(task->exit_state == 0);
> - pid = task_pid(task);
> - wake_up_all(&pid->wait_pidfd);
> +
> + __wake_up(&pid->wait_pidfd, TASK_NORMAL, 0,
> + poll_to_key(EPOLLIN | EPOLLRDNORM));
> }
>
> /*
> --
> 2.25.1.362.g51ebf55
>
>
next prev parent reply other threads:[~2024-02-05 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 14:10 [PATCH] pidfd: change do_notify_pidfd() to use __wake_up(poll_to_key(EPOLLIN)) Oleg Nesterov
2024-02-05 14:22 ` Oleg Nesterov [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 14:13 Oleg Nesterov
2024-02-06 12:53 ` Christian Brauner
2024-02-06 17:03 ` Tycho Andersen
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=20240205142229.GA16757@redhat.com \
--to=oleg@redhat.com \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=tycho@tycho.pizza \
/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