oom_ajd: don't use WARN_ONCE, just use printk_once
authorLinus Torvalds <torvalds@linux-foundation.org>
Sat, 6 Aug 2011 18:43:08 +0000 (11:43 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Sat, 6 Aug 2011 18:43:08 +0000 (11:43 -0700)
commitc21427043dec93d40e3a1af970831d1f5f15ce5d
treead5a6fc418ffb6459f6e75bfa47ecd12c5606267
parent1eb19a12bd2214cdcad5273d472b062a4ba97fa1
oom_ajd: don't use WARN_ONCE, just use printk_once

WARN_ONCE() is very annoying, in that it shows the stack trace that we
don't care about at all, and also triggers various user-level "kernel
oopsed" logic that we really don't care about.  And it's not like the
user can do anything about the applications (sshd) in question, it's a
distro issue.

Requested-by: Andi Kleen <andi@firstfloor.org> (and many others)
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
fs/proc/base.c