netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net] ptr_ring: fail early if queue occupies more than KMALLOC_MAX_SIZE
Date: Wed, 7 Feb 2018 17:15:35 +0200	[thread overview]
Message-ID: <20180207171422-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <14eecede-e053-9f97-cc09-5ab58cd4d2cf@redhat.com>

On Wed, Feb 07, 2018 at 05:17:59PM +0800, Jason Wang wrote:
> 
> 
> On 2018年02月07日 16:08, Jason Wang wrote:
> > To avoid slab to warn about exceeded size, fail early if queue
> > occupies more than KMALLOC_MAX_SIZE.
> > 
> > Reported-by: syzbot+e4d4f9ddd4295539735d@syzkaller.appspotmail.com
> > Signed-off-by: Jason Wang <jasowang@redhat.com>
> > ---
> >   include/linux/ptr_ring.h | 2 ++
> >   1 file changed, 2 insertions(+)
> > 
> > diff --git a/include/linux/ptr_ring.h b/include/linux/ptr_ring.h
> > index 1883d61..4b862da 100644
> > --- a/include/linux/ptr_ring.h
> > +++ b/include/linux/ptr_ring.h
> > @@ -466,6 +466,8 @@ static inline int ptr_ring_consume_batched_bh(struct ptr_ring *r,
> >   static inline void **__ptr_ring_init_queue_alloc(unsigned int size, gfp_t gfp)
> >   {
> > +	if (size > KMALLOC_MAX_SIZE)
> > +		return NULL;
> >   	return kcalloc(size, sizeof(void *), gfp);
> >   }
> 
> Fixes: 2e0ab8ca83c12 ("ptr_ring: array based FIFO for pointers")

That's probably not enough. How about switching to kvmalloc and limiting
this drastically to e.g. 64K. I vaguely remember that some wise man said
that should be enough for everybody :)

-- 
MST

  reply	other threads:[~2018-02-07 15:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07  8:08 [PATCH net] ptr_ring: fail early if queue occupies more than KMALLOC_MAX_SIZE Jason Wang
2018-02-07  9:17 ` Jason Wang
2018-02-07 15:15   ` Michael S. Tsirkin [this message]
2018-02-08  3:04     ` Jason Wang
2018-02-08 15:44 ` Michael S. Tsirkin

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=20180207171422-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).