kernel/printk.c: document possible deadlock against scheduler
commit1492192b4a0bb84dd9b792cc0bd30583220a28a7
authorJiri Kosina <jkosina@suse.cz>
Mon, 16 Jul 2007 06:41:51 +0000 (15 23:41 -0700)
committerLinus Torvalds <torvalds@woody.linux-foundation.org>
Mon, 16 Jul 2007 16:05:52 +0000 (16 09:05 -0700)
tree54763778f2c1ed69ae967022dd940b4bcc040120
parent017f021c7e5fe3f82ccc5cbb7b1750e66e00f527
kernel/printk.c: document possible deadlock against scheduler

kernel/printk.c: document possible deadlock against scheduler

The printk's comment states that it can be called from every context,
which might lead to false illusion that it could be called from everywhere
without any restrictions.

This is however not true - a call to printk() could deadlock if called from
scheduler code (namely from schedule(), wake_up(), etc) on runqueue lock
when it tries to wake up klogd. Document this.

Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
kernel/printk.c