mm: don't let userspace spam allocations warnings
memdump_user usually gets fed unchecked userspace input. Blasting a
full backtrace into dmesg every time is a bit excessive - I'm not sure
on the kernel rule in general, but at least in drm we're trying not to
let unpriviledge userspace spam the logs freely. Definitely not entire
warning backtraces.
It also means more filtering for our CI, because our testsuite exercises
these corner cases and so hits these a lot.
Link: http://lkml.kernel.org/r/20190220204058.11676-1-daniel.vetter@ffwll.ch
Signed-off-by: Daniel Vetter <daniel.vetter at intel.com>
Reviewed-by: Andrew Morton <akpm at linux-foundation.org>
Acked-by: Michal Hocko <mhocko at suse.com>
Reviewed-by: Kees Cook <keescook at chromium.org>
Cc: Mike Rapoport <rppt at linux.vnet.ibm.com>
Cc: Roman Gushchin <guro at fb.com>
Cc: Vlastimil Babka <vbabka at suse.cz>
Cc: Jan Stancek <jstancek at redhat.com>
Cc: Andrey Ryabinin <aryabinin at virtuozzo.com>
Cc: "Michael S. Tsirkin" <mst at redhat.com>
Cc: Huang Ying <ying.huang at intel.com>
Cc: Bartosz Golaszewski <brgl at bgdev.pl>
Signed-off-by: Andrew Morton <akpm at linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds at linux-foundation.org>
UnifiedSplitRaw
