From: Oleg Nesterov <oleg@redhat.com>
To: Aviv Vaknin <vaknins33@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Bradley Morgan <brads@mainlining.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] pid_namespace: make zap_pid_ns_processes() freezable
Date: Sat, 3 Oct 2026 13:06:59 +0200 [thread overview]
Message-ID: <asDh0zBHEIWdto5x@redhat.com> (raw)
In-Reply-To: <20261002202820.3433318-1-vaknins33@gmail.com>
On 10/02, Aviv Vaknin wrote:
>
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -1751,7 +1751,7 @@ static long do_wait(struct wait_opts *wo)
> add_wait_queue(¤t->signal->wait_chldexit, &wo->child_wait);
>
> do {
> - set_current_state(TASK_INTERRUPTIBLE);
> + set_current_state(TASK_INTERRUPTIBLE | TASK_FREEZABLE);
> retval = __do_wait(wo);
> if (retval != -ERESTARTSYS)
> break;
> diff --git a/kernel/pid_namespace.c b/kernel/pid_namespace.c
> index 8bc9edb40..127a5fd23 100644
> --- a/kernel/pid_namespace.c
> +++ b/kernel/pid_namespace.c
> @@ -269,7 +269,7 @@ void zap_pid_ns_processes(struct pid_namespace *pid_ns)
> * free_pid() will awaken this task.
> */
> for (;;) {
> - set_current_state(TASK_INTERRUPTIBLE);
> + set_current_state(TASK_IDLE | TASK_FREEZABLE);
> if (pid_ns->pid_allocated == init_pids)
> break;
> schedule();
Thanks Aviv,
Acked-by: Oleg Nesterov <oleg@redhat.com>
prev parent reply other threads:[~2026-10-03 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 20:28 [PATCH v2] pid_namespace: make zap_pid_ns_processes() freezable Aviv Vaknin
2026-10-02 20:30 ` Bradley Morgan
2026-10-03 11:06 ` Oleg Nesterov [this message]
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=asDh0zBHEIWdto5x@redhat.com \
--to=oleg@redhat.com \
--cc=brads@mainlining.org \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vaknins33@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 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.