From: Marco Elver <elver@google.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
Dmitry Vyukov <dvyukov@google.com>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: linux-next: Tree for Nov 19 (kcsan)
Date: Tue, 19 Nov 2019 17:12:16 +0100 [thread overview]
Message-ID: <CANpmjNMpnY54kDdGwOPOD84UDf=Fzqtu62ifTds2vZn4t4YigQ@mail.gmail.com> (raw)
In-Reply-To: <e75be639-110a-c615-3ec7-a107318b7746@infradead.org>
On Tue, 19 Nov 2019 at 16:11, Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 11/19/19 12:46 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20191118:
> >
>
> on x86_64:
>
> It seems that this function can already be known by the compiler as a
> builtin:
>
> ../kernel/kcsan/core.c:619:6: warning: conflicting types for built-in function ‘__tsan_func_exit’ [-Wbuiltin-declaration-mismatch]
> void __tsan_func_exit(void)
> ^~~~~~~~~~~~~~~~
>
>
> $ gcc --version
> gcc (SUSE Linux) 7.4.1 20190905 [gcc-7-branch revision 275407]
Interesting. Could you share the .config? So far I haven't been able
to reproduce.
I can get the warning if I manually add -fsanitize=thread to flags for
kcsan/core.c (but normally disabled via KCSAN_SANITIZE := n). If
possible could you also share the output of `make V=1` for
kcsan/core.c?
Thanks,
-- Marco
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2019-11-19 16:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 8:46 linux-next: Tree for Nov 19 Stephen Rothwell
2019-11-19 15:11 ` linux-next: Tree for Nov 19 (kcsan) Randy Dunlap
2019-11-19 16:12 ` Marco Elver [this message]
2019-11-19 16:50 ` Randy Dunlap
2019-11-19 18:34 ` Marco Elver
2019-11-19 18:57 ` [PATCH -next] kcsan, ubsan: Make KCSAN+UBSAN work together Marco Elver
2019-11-19 20:16 ` Paul E. McKenney
2019-11-19 21:07 ` Randy Dunlap
2019-11-19 21:17 ` Paul E. McKenney
2019-11-19 19:02 ` linux-next: Tree for Nov 19 (kcsan) Qian Cai
2019-11-19 19:05 ` Marco Elver
2019-11-19 20:14 ` Paul E. McKenney
2019-11-19 15:13 ` linux-next: Tree for Nov 19 (bpf) Randy Dunlap
2019-11-27 23:45 ` linux-next: Tree for Nov 19 (bpf/btf) Randy Dunlap
2019-11-19 15:33 ` linux-next: Tree for Nov 19 (i915) Randy Dunlap
2019-11-20 16:15 ` [Intel-gfx] " Jani Nikula
2019-11-20 16:56 ` Chris Wilson
2019-11-20 21:54 ` Randy Dunlap
2019-11-19 15:38 ` linux-next: Tree for Nov 19 (objtool) Randy Dunlap
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='CANpmjNMpnY54kDdGwOPOD84UDf=Fzqtu62ifTds2vZn4t4YigQ@mail.gmail.com' \
--to=elver@google.com \
--cc=dvyukov@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).