diff options
| author | Kirill Korotaev <dev@openvz.org> | 2006-06-23 02:03:50 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-06-23 07:42:52 -0700 |
| commit | 8f9de51a4a98ba32f839903b7d009788bc2c295d (patch) | |
| tree | 65cde3cd75bfc1df172f53ca956cba4fa4954a4e /kernel/spinlock.c | |
| parent | d501e62bc7796e90b0312648e23ac39490dfbf87 (diff) | |
| download | blackbird-op-linux-8f9de51a4a98ba32f839903b7d009788bc2c295d.tar.gz blackbird-op-linux-8f9de51a4a98ba32f839903b7d009788bc2c295d.zip | |
[PATCH] printk() should not be called under zone->lock
This patch fixes printk() under zone->lock in show_free_areas(). It can be
unsafe to call printk() under this lock, since caller can try to
allocate/free some memory and selfdeadlock on this lock. I found
allocations/freeing mem both in netconsole and serial console.
This issue was faced in reallity when meminfo was periodically printed for
debug purposes and netconsole was used.
Signed-off-by: Kirill Korotaev <dev@openvz.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'kernel/spinlock.c')
0 files changed, 0 insertions, 0 deletions
