From: Tejun Heo <tj@kernel.org>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: rjw@sisk.pl, pavel@ucw.cz, lenb@kernel.org, ak@linux.intel.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2] PM/Memory-hotplug: Avoid task freezing failures
Date: Wed, 16 Nov 2011 08:26:24 -0800 [thread overview]
Message-ID: <20111116162601.GB18919@google.com> (raw)
In-Reply-To: <20111116115515.25945.35368.stgit@srivatsabhat.in.ibm.com>
Hello,
On Wed, Nov 16, 2011 at 05:25:23PM +0530, Srivatsa S. Bhat wrote:
> v2: Tejun pointed problems with using mutex_lock_interruptible() in a
> while loop, when signals not related to freezing are involved.
> So, replaced it with mutex_trylock().
>
> Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
> ---
>
> include/linux/suspend.h | 14 +++++++++++++-
> 1 files changed, 13 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/suspend.h b/include/linux/suspend.h
> index 57a6924..c2b5aab 100644
> --- a/include/linux/suspend.h
> +++ b/include/linux/suspend.h
> @@ -5,6 +5,7 @@
> #include <linux/notifier.h>
> #include <linux/init.h>
> #include <linux/pm.h>
> +#include <linux/freezer.h>
> #include <linux/mm.h>
> #include <asm/errno.h>
>
> @@ -380,7 +381,18 @@ static inline void unlock_system_sleep(void) {}
>
> static inline void lock_system_sleep(void)
> {
> - mutex_lock(&pm_mutex);
> + /*
> + * We should not use mutex_lock() here because, in case we fail to
> + * acquire the lock, it would put us to sleep in TASK_UNINTERRUPTIBLE
> + * state, which would lead to task freezing failures. As a
> + * consequence, hibernation would fail (even though it had acquired
> + * the 'pm_mutex' lock).
> + *
> + * We should use try_to_freeze() in the while loop so that we don't
> + * cause freezing failures due to busy looping.
> + */
> + while (!mutex_trylock(&pm_mutex))
> + try_to_freeze();
I'm kinda lost. We now always busy-loop if the lock is held by
someone else. I can't see how that is an improvement. If this isn't
an immediate issue, wouldn't it be better to wait for proper solution?
Thank you.
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-11-16 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 11:55 Srivatsa S. Bhat
2011-11-16 16:26 ` Tejun Heo [this message]
2011-11-16 17:22 ` Srivatsa S. Bhat
2011-11-16 17:43 ` Tejun Heo
2011-11-16 18:24 ` Srivatsa S. Bhat
2011-11-16 18:41 ` Tejun Heo
2011-11-16 19:05 ` Srivatsa S. Bhat
2011-11-16 21:47 ` Rafael J. Wysocki
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=20111116162601.GB18919@google.com \
--to=tj@kernel.org \
--cc=ak@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox