summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorMichal Hocko <mhocko@suse.com>2018-06-08 03:09:40 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2018-06-08 03:34:38 +0300
commitce91f6ee5b3bbbad8caff61b1c46d845c8db19bf (patch)
tree6b15942c9c8f673dc94a9dbc824e778f2ef8ff2a /tools
parent4b33b6959581d5093af2badb489d914911d99eaf (diff)
downloadlinux-ce91f6ee5b3bbbad8caff61b1c46d845c8db19bf.tar.xz
mm: kvmalloc does not fallback to vmalloc for incompatible gfp flags
kvmalloc warned about incompatible gfp_mask to catch abusers (mostly GFP_NOFS) with an intention that this will motivate authors of the code to fix those. Linus argues that this just motivates people to do even more hacks like if (gfp == GFP_KERNEL) kvmalloc else kmalloc I haven't seen this happening much (Linus pointed to bucket_lock special cases an atomic allocation but my git foo hasn't found much more) but it is true that we can grow those in future. Therefore Linus suggested to simply not fallback to vmalloc for incompatible gfp flags and rather stick with the kmalloc path. Link: http://lkml.kernel.org/r/20180601115329.27807-1-mhocko@kernel.org Signed-off-by: Michal Hocko <mhocko@suse.com> Suggested-by: Linus Torvalds <torvalds@linux-foundation.org> Cc: Tom Herbert <tom@quantonium.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions