[PATCH] printk() should not be called under zone->lock
authorKirill Korotaev <dev@openvz.org>
Fri, 23 Jun 2006 09:03:50 +0000 (02:03 -0700)
committerLinus Torvalds <torvalds@g5.osdl.org>
Fri, 23 Jun 2006 14:42:52 +0000 (07:42 -0700)
commit8f9de51a4a98ba32f839903b7d009788bc2c295d
tree65cde3cd75bfc1df172f53ca956cba4fa4954a4e
parentd501e62bc7796e90b0312648e23ac39490dfbf87
[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>
mm/page_alloc.c