From: Pablo Neira Ayuso <pablo@netfilter.org>
To: ZhangXiaoxu <zhangxiaoxu5@huawei.com>
Cc: wensong@linux-vs.org, horms@verge.net.au, ja@ssi.bg,
netdev@vger.kernel.org, lvs-devel@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] ipvs: Fix signed integer overflow when setsockopt timeout
Date: Thu, 24 Jan 2019 13:32:04 +0100 [thread overview]
Message-ID: <20190124123204.yllpivzdshofap6z@salvia> (raw)
In-Reply-To: <1547109546-11344-1-git-send-email-zhangxiaoxu5@huawei.com>
On Thu, Jan 10, 2019 at 04:39:06PM +0800, ZhangXiaoxu wrote:
> There is a UBSAN bug report as below:
> UBSAN: Undefined behaviour in net/netfilter/ipvs/ip_vs_ctl.c:2227:21
> signed integer overflow:
> -2147483647 * 1000 cannot be represented in type 'int'
Applied, thanks.
prev parent reply other threads:[~2019-01-24 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 8:39 [PATCH] ipvs: Fix signed integer overflow when setsockopt timeout ZhangXiaoxu
2019-01-14 7:34 ` zhangxiaoxu (A)
2019-01-14 12:15 ` Simon Horman
2019-01-24 12:22 ` zhangxiaoxu (A)
2019-01-24 12:32 ` Pablo Neira Ayuso [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=20190124123204.yllpivzdshofap6z@salvia \
--to=pablo@netfilter.org \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=wensong@linux-vs.org \
--cc=zhangxiaoxu5@huawei.com \
/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