printk: robustify printk, update comment

Jiri Kosina · Ingo Molnar · commit 1fa63a817d27 · 2008-08-20T15:39:59.000+02:00
Remove the comment describing the possibility of printk() deadlocking on
runqueue lock.

Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
Acked-by: Peter Zijlstra &lt;a.p.zijlstra@chello.nl&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
diff --git 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

Original file line number	Diff line number	Diff line change
`@@ -577,9 +577,6 @@ static int have_callable_console(void)`
`577`	`577`	`* @fmt: format string`
`578`	`578`	`*`
`579`	`579`	`* This is printk(). It can be called from any context. We want it to work.`
`580`		`- * Be aware of the fact that if oops_in_progress is not set, we might try to`
`581`		`- * wake klogd up which could deadlock on runqueue lock if printk() is called`
`582`		`- * from scheduler code.`
`583`	`580`	`*`
`584`	`581`	`* We try to grab the console_sem. If we succeed, it's easy - we log the output and`
`585`	`582`	`* call the console drivers. If we fail to get the semaphore we place the output`