From: David Miller <davem@davemloft.net>
To: jasowang@redhat.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
mst@redhat.com, ebiggers3@gmail.com
Subject: Re: [PATCH net] ptr_ring: prevent integer overflow when calculating size
Date: Sun, 11 Feb 2018 22:34:50 -0500 (EST) [thread overview]
Message-ID: <20180211.223450.926436849855081876.davem@davemloft.net> (raw)
In-Reply-To: <1518319692-5421-1-git-send-email-jasowang@redhat.com>
From: Jason Wang <jasowang@redhat.com>
Date: Sun, 11 Feb 2018 11:28:12 +0800
> Switch to use dividing to prevent integer overflow when size is too
> big to calculate allocation size properly.
>
> Reported-by: Eric Biggers <ebiggers3@gmail.com>
> Fixes: 6e6e41c31122 ("ptr_ring: fail early if queue occupies more than KMALLOC_MAX_SIZE")
> Signed-off-by: Jason Wang <jasowang@redhat.com>
Applied and queued up for -stable, thanks Jason.
prev parent reply other threads:[~2018-02-12 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 3:28 [PATCH net] ptr_ring: prevent integer overflow when calculating size Jason Wang
2018-02-11 22:02 ` Michael S. Tsirkin
2018-02-12 3:34 ` David Miller [this message]
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=20180211.223450.926436849855081876.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ebiggers3@gmail.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--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).