From: Peter Zijlstra <peterz@infradead.org>
To: Eric Dumazet <edumazet@google.com>
Cc: kernel test robot <rong.a.chen@intel.com>,
Yuqi Jin <jinyuqi@huawei.com>,
"David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@resnulli.us>,
Arvind Sankar <nivedita@alum.mit.edu>,
Jiong Wang <jiongwang@huawei.com>,
Shaokun Zhang <zhangshaokun@hisilicon.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org
Subject: Re: [net] a6211caa63: dmesg.UBSAN:signed-integer-overflow_in_arch/x86/include/asm/atomic.h
Date: Fri, 5 Jun 2020 16:05:21 +0200 [thread overview]
Message-ID: <20200605140521.GD4117@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CANn89iK1EfAqw-SkXyQR=88fKnBpXCcR_FaiFkVDUNazNgAX1g@mail.gmail.com>
On Fri, Jun 05, 2020 at 06:17:51AM -0700, Eric Dumazet wrote:
> On Fri, Jun 5, 2020 at 1:10 AM kernel test robot <rong.a.chen@intel.com> wrote:
> There you go.
>
> We decided this was a bogus report, and that UBSAN requires sane compilers.
>
> Please read the fine comment that was added in this commit and update
> your compiler or do not mess with compiler flags.
>
> + /* If UBSAN reports an error there, please make sure your compiler
> + * supports -fno-strict-overflow before reporting it that was a bug
> + * in UBSAN, and it has been fixed in GCC-8.
> + */
> + return atomic_add_return(segs + delta, p_id) - segs;
> > make HOSTCC=gcc-4.9 CC=gcc-4.9 ARCH=i386 olddefconfig prepare modules_prepare bzImage
Rong, can you make sure to exclude gcc<8 for UBSAN reports ?
next prev parent reply other threads:[~2020-06-05 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 8:09 kernel test robot
2020-06-05 13:17 ` Eric Dumazet
2020-06-05 14:05 ` Peter Zijlstra [this message]
2020-06-06 3:03 ` Chen, Rong A
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=20200605140521.GD4117@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jinyuqi@huawei.com \
--cc=jiongwang@huawei.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=nivedita@alum.mit.edu \
--cc=rong.a.chen@intel.com \
--cc=yoshfuji@linux-ipv6.org \
--cc=zhangshaokun@hisilicon.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
all inboxes | Powered by JetHome®