diff options
author | Jiri Kosina <jkosina@suse.cz> | 2008-08-20 14:40:55 +0200 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2008-08-20 15:39:59 +0200 |
commit | 1fa63a817d27af7dc0d5ed454eb8fe5dec65fac7 (patch) | |
tree | 32da7727193eeb85cb71e8b347afce76997abe89 | |
parent | fa33507a22623b3bd543b15a21c362cf364b6cff (diff) | |
download | op-kernel-dev-1fa63a817d27af7dc0d5ed454eb8fe5dec65fac7.zip op-kernel-dev-1fa63a817d27af7dc0d5ed454eb8fe5dec65fac7.tar.gz |
printk: robustify printk, update comment
Remove the comment describing the possibility of printk() deadlocking on
runqueue lock.
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
-rw-r--r-- | kernel/printk.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/kernel/printk.c b/kernel/printk.c index 57e9cd7..6f27c6a 100644 --- a/kernel/printk.c +++ b/kernel/printk.c @@ -577,9 +577,6 @@ static int have_callable_console(void) * @fmt: format string * * This is printk(). It can be called from any context. We want it to work. - * Be aware of the fact that if oops_in_progress is not set, we might try to - * wake klogd up which could deadlock on runqueue lock if printk() is called - * from scheduler code. * * We try to grab the console_sem. If we succeed, it's easy - we log the output and * call the console drivers. If we fail to get the semaphore we place the output |