[lkml]   [2017]   [Dec]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: WARNING in kmalloc_slab (3)
On Mon, Dec 4, 2017 at 9:14 AM, Dan Carpenter <> wrote:
> On Sun, Dec 03, 2017 at 12:16:08PM -0800, Eric Biggers wrote:
>> Looks like BLKTRACESETUP doesn't limit the '.buf_nr' parameter, allowing anyone
>> who can open a block device to cause an extremely large kmalloc. Here's a
>> simplified reproducer:
> There are lots of places which allow people to allocate as much as they
> want. With Syzcaller, you might want to just hard code a __GFP_NOWARN
> in to disable it.


Hard code it where?

User-controllable allocation are supposed to use __GFP_NOWARN.

 \ /
  Last update: 2017-12-04 09:18    [W:0.108 / U:14.584 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site