linux/drivers/staging/android
Laura Abbott 0c75f10312 staging: android: ion: Add __GFP_NOWARN for system contig heap
syzbot reported a warning from Ion:

  WARNING: CPU: 1 PID: 3485 at mm/page_alloc.c:3926

  ...
   __alloc_pages_nodemask+0x9fb/0xd80 mm/page_alloc.c:4252
  alloc_pages_current+0xb6/0x1e0 mm/mempolicy.c:2036
  alloc_pages include/linux/gfp.h:492 [inline]
  ion_system_contig_heap_allocate+0x40/0x2c0
  drivers/staging/android/ion/ion_system_heap.c:374
  ion_buffer_create drivers/staging/android/ion/ion.c:93 [inline]
  ion_alloc+0x2c1/0x9e0 drivers/staging/android/ion/ion.c:420
  ion_ioctl+0x26d/0x380 drivers/staging/android/ion/ion-ioctl.c:84
  vfs_ioctl fs/ioctl.c:46 [inline]
  do_vfs_ioctl+0x1b1/0x1520 fs/ioctl.c:686
  SYSC_ioctl fs/ioctl.c:701 [inline]
  SyS_ioctl+0x8f/0xc0 fs/ioctl.c:692

This is a warning about attempting to allocate order > MAX_ORDER. This
is coming from a userspace Ion allocation request. Since userspace is
free to request however much memory it wants (and the kernel is free to
deny its allocation), silence the allocation attempt with __GFP_NOWARN
in case it fails.

Reported-by: syzbot+76e7efc4748495855a4d@syzkaller.appspotmail.com
Reported-by: syzbot <syzkaller@googlegroups.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-01-09 15:38:48 +01:00
..
ion staging: android: ion: Add __GFP_NOWARN for system contig heap 2018-01-09 15:38:48 +01:00
uapi staging: android: Remove redundant license text 2017-11-28 13:20:48 +01:00
ashmem.c staging: android: check the return value of register_shrinker 2018-01-08 16:37:18 +01:00
ashmem.h staging: android: add SPDX identifiers to all android driver files 2017-11-28 13:20:47 +01:00
Kconfig staging, android: remove lowmemory killer from the tree 2017-03-09 13:47:03 +01:00
Makefile staging, android: remove lowmemory killer from the tree 2017-03-09 13:47:03 +01:00
TODO staging: android: TODO: Removing an invalid issue 2017-10-03 18:36:57 +02:00