diff options
| author | Jiri Kosina <jkosina@suse.cz> | 2007-07-16 02:41:51 -0400 |
|---|---|---|
| committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-07-16 12:05:52 -0400 |
| commit | 1492192b4a0bb84dd9b792cc0bd30583220a28a7 (patch) | |
| tree | 54763778f2c1ed69ae967022dd940b4bcc040120 /include/linux | |
| parent | 017f021c7e5fe3f82ccc5cbb7b1750e66e00f527 (diff) | |
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>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions