From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
pavel@ucw.cz, len.brown@intel.com, tj@kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/2] PM / Freezer: Remove the "userspace only" constraint from freezer[_do_not]_count()
Date: Tue, 6 Dec 2011 23:36:40 +0100 [thread overview]
Message-ID: <201112062336.40846.rjw@sisk.pl> (raw)
In-Reply-To: <4EDE5AE1.2080607@linux.vnet.ibm.com>
On Tuesday, December 06, 2011, Srivatsa S. Bhat wrote:
> On 12/06/2011 10:50 PM, Oleg Nesterov wrote:
>
> > On 12/06, Srivatsa S. Bhat wrote:
> >>
> >> And moreover, even the vfork issue does not need
> >> the above restriction in these functions, since they are anyway called by
> >> userspace processes.
> >
> > This looks a bit confusing, as if CLONE_VFORK is not used by kthreads.
> > It is actually used, but only by the non-freezeable workqueue threads,
> > so the patch is fine.
> >
> > Reviewed-by: Oleg Nesterov <oleg@redhat.com>
> >
>
>
> Thank you! I have updated the commit message by omitting the confusing part:
>
> ---
> From: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
> [PATCH 1/2] PM / Freezer: Remove the "userspace only" constraint from freezer[_do_not]_count()
>
> At present, the functions freezer_count() and freezer_do_not_count()
> impose the restriction that they are effective only for userspace processes.
> However, now, these functions have found more utility than originally
> intended by the commit which introduced it: ba96a0c8 (freezer:
> fix vfork problem). And moreover, even the vfork issue actually does not
> need the above restriction in these functions.
>
> So, modify these functions to make them work even for kernel threads, so
> that they can be used at other places in the kernel, where the userspace
> restriction doesn't apply.
>
> Suggested-by: Oleg Nesterov <oleg@redhat.com>
> Suggested-by: Tejun Heo <tj@kernel.org>
> Acked-by: Tejun Heo <tj@kernel.org>
> Reviewed-by: Oleg Nesterov <oleg@redhat.com>
> Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
Applied to linux-pm/linux-next ([2/2] too).
Thanks,
Rafael
> ---
>
> include/linux/freezer.h | 28 +++++++++++-----------------
> 1 files changed, 11 insertions(+), 17 deletions(-)
>
> diff --git a/include/linux/freezer.h b/include/linux/freezer.h
> index 30f06c2..7bcfe73 100644
> --- a/include/linux/freezer.h
> +++ b/include/linux/freezer.h
> @@ -67,33 +67,27 @@ static inline bool cgroup_freezing(struct task_struct *task)
> * appropriately in case the child has exited before the freezing of tasks is
> * complete. However, we don't want kernel threads to be frozen in unexpected
> * places, so we allow them to block freeze_processes() instead or to set
> - * PF_NOFREEZE if needed and PF_FREEZER_SKIP is only set for userland vfork
> - * parents. Fortunately, in the ____call_usermodehelper() case the parent won't
> - * really block freeze_processes(), since ____call_usermodehelper() (the child)
> - * does a little before exec/exit and it can't be frozen before waking up the
> - * parent.
> + * PF_NOFREEZE if needed. Fortunately, in the ____call_usermodehelper() case the
> + * parent won't really block freeze_processes(), since ____call_usermodehelper()
> + * (the child) does a little before exec/exit and it can't be frozen before
> + * waking up the parent.
> */
>
> -/*
> - * If the current task is a user space one, tell the freezer not to count it as
> - * freezable.
> - */
> +
> +/* Tell the freezer not to count the current task as freezable. */
> static inline void freezer_do_not_count(void)
> {
> - if (current->mm)
> - current->flags |= PF_FREEZER_SKIP;
> + current->flags |= PF_FREEZER_SKIP;
> }
>
> /*
> - * If the current task is a user space one, tell the freezer to count it as
> - * freezable again and try to freeze it.
> + * Tell the freezer to count the current task as freezable again and try to
> + * freeze it.
> */
> static inline void freezer_count(void)
> {
> - if (current->mm) {
> - current->flags &= ~PF_FREEZER_SKIP;
> - try_to_freeze();
> - }
> + current->flags &= ~PF_FREEZER_SKIP;
> + try_to_freeze();
> }
>
> /*
>
>
>
>
prev parent reply other threads:[~2011-12-06 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 16:03 Srivatsa S. Bhat
2011-12-06 16:04 ` [PATCH 2/2] PM: Use the freezer_count() functions in [un]lock_system_sleep() APIs Srivatsa S. Bhat
2011-12-06 16:35 ` Tejun Heo
2011-12-06 16:35 ` [PATCH 1/2] PM / Freezer: Remove the "userspace only" constraint from freezer[_do_not]_count() Tejun Heo
2011-12-06 17:20 ` Oleg Nesterov
2011-12-06 18:11 ` Srivatsa S. Bhat
2011-12-06 22:36 ` Rafael J. Wysocki [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=201112062336.40846.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pavel@ucw.cz \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tj@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
Powered by JetHome