From: "Arve Hjønnevåg" <arve@android.com>
To: linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Cc: swetland@google.com, pavel@ucw.cz, "Arve Hjønnevåg" <arve@android.com>
Subject: [PATCH 2/2] PM: Fix suspend_console/resume_console to use only one semaphore.
Date: Fri, 30 Jan 2009 19:27:39 -0800 [thread overview]
Message-ID: <1233372459-6434-2-git-send-email-arve@android.com> (raw)
In-Reply-To: <1233372459-6434-1-git-send-email-arve@android.com>
This fixes a race if another thread acquired the console
while it was suspended and released it after it was resumed
the secondary console semaphre would be left locked, and the
primary semaphore would be released twice. This in turn caused
the console switch on suspend or resume to hang forever.
Note that suspend_console does not actually lock the console
for clients that use acquire_console_sem, it only locks it for
clients that use try_acquire_console_sem. If we change
suspend_console to fully lock the console, then the kernel
may deadlock on suspend.
Signed-off-by: Arve Hjønnevåg <arve@android.com>
---
kernel/printk.c | 15 +++++++++------
1 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/kernel/printk.c b/kernel/printk.c
index 7015733..118ee77 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -73,7 +73,6 @@ EXPORT_SYMBOL(oops_in_progress);
* driver system.
*/
static DECLARE_MUTEX(console_sem);
-static DECLARE_MUTEX(secondary_console_sem);
struct console *console_drivers;
EXPORT_SYMBOL_GPL(console_drivers);
@@ -896,12 +895,14 @@ void suspend_console(void)
printk("Suspending console(s) (use no_console_suspend to debug)\n");
acquire_console_sem();
console_suspended = 1;
+ up(&console_sem);
}
void resume_console(void)
{
if (!console_suspend_enabled)
return;
+ down(&console_sem);
console_suspended = 0;
release_console_sem();
}
@@ -917,11 +918,9 @@ void resume_console(void)
void acquire_console_sem(void)
{
BUG_ON(in_interrupt());
- if (console_suspended) {
- down(&secondary_console_sem);
- return;
- }
down(&console_sem);
+ if (console_suspended)
+ return;
console_locked = 1;
console_may_schedule = 1;
}
@@ -931,6 +930,10 @@ int try_acquire_console_sem(void)
{
if (down_trylock(&console_sem))
return -1;
+ if (console_suspended) {
+ up(&console_sem);
+ return -1;
+ }
console_locked = 1;
console_may_schedule = 0;
return 0;
@@ -984,7 +987,7 @@ void release_console_sem(void)
unsigned wake_klogd = 0;
if (console_suspended) {
- up(&secondary_console_sem);
+ up(&console_sem);
return;
}
--
1.6.1
next prev parent reply other threads:[~2009-01-31 3:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 1:07 [PATCH 0/2] Android PM fixes Arve Hjønnevåg
2009-01-14 1:07 ` [PATCH 1/2] PM: Wait for console in resume Arve Hjønnevåg
2009-01-14 1:07 ` [PATCH 2/2] PM: Fix suspend_console/resume_console to use only one semaphore Arve Hjønnevåg
2009-01-28 19:30 ` Pavel Machek
2009-01-31 3:27 ` [PATCH 1/2] PM: Wait for console in resume Arve Hjønnevåg
2009-01-31 3:27 ` Arve Hjønnevåg
2009-01-31 3:27 ` [PATCH 2/2] PM: Fix suspend_console/resume_console to use only one semaphore Arve Hjønnevåg
2009-01-31 3:27 ` Arve Hjønnevåg [this message]
2009-02-03 2:03 ` [PATCH] " Arve Hjønnevåg
2009-02-03 2:03 ` Arve Hjønnevåg
2009-02-08 2:36 ` [linux-pm] " Benjamin Herrenschmidt
2009-02-08 2:36 ` Benjamin Herrenschmidt
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=1233372459-6434-2-git-send-email-arve@android.com \
--to=arve@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=swetland@google.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.