linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: syzbot 
	<bot+2797c18fc195e3e240c3c3e7837a14130e157fb0@syzkaller.appspotmail.com>,
	adobriyan@gmail.com, akpm@linux-foundation.org, arnd@arndb.de,
	dave.jiang@intel.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
	linux-block@vger.kernel.org
Subject: Re: WARNING in kmalloc_slab (3)
Date: Mon, 4 Dec 2017 11:14:08 +0300	[thread overview]
Message-ID: <20171204081408.oyp46roxbkjbxxkw@mwanda> (raw)
In-Reply-To: <20171203201608.GC844@zzz.localdomain>

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.

regards,
dan carpenter

  reply	other threads:[~2017-12-04 11:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 14:25 WARNING in kmalloc_slab (3) syzbot
2017-12-03 20:16 ` Eric Biggers
2017-12-04  8:14   ` Dan Carpenter [this message]
2017-12-04  8:18     ` Dmitry Vyukov
2017-12-04  9:26       ` Dan Carpenter
2017-12-12 15:50         ` Dmitry Vyukov
2017-12-12 21:22         ` Eric Biggers
2018-02-07  4:58           ` Dmitry Vyukov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171204081408.oyp46roxbkjbxxkw@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bot+2797c18fc195e3e240c3c3e7837a14130e157fb0@syzkaller.appspotmail.com \
    --cc=dave.jiang@intel.com \
    --cc=ebiggers3@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).