From: Will Deacon <will@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Marco Elver <elver@google.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Kees Cook <keescook@chromium.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Arvind Sankar <nivedita@alum.mit.edu>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Alexander Potapenko <glider@google.com>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] kcsan: fix section mismatch for __write_once_size/blacklisted_initcalls
Date: Tue, 5 May 2020 16:11:50 +0100 [thread overview]
Message-ID: <20200505151150.GD24239@willie-the-truck> (raw)
In-Reply-To: <CAK8P3a3r35VrKVfpn_q2YYhxkvH9j0+3MnMqgRM6R=QOcsE96Q@mail.gmail.com>
On Tue, May 05, 2020 at 05:05:36PM +0200, Arnd Bergmann wrote:
> On Tue, May 5, 2020 at 4:17 PM 'Marco Elver' via Clang Built Linux
> <clang-built-linux@googlegroups.com> wrote:
> > On Tue, 5 May 2020 at 16:11, Arnd Bergmann <arnd@arndb.de> wrote:
> > > So far, my randconfig checks found two such instances, one for read_once
> > > and one for write_once. There are probably a couple more in random
> > > configurations, but I guess they are rare enough that we can just work
> > > around them like this.
> >
> > [+Cc Will]
> >
> > Thanks for testing and fixing this. Note that this may no longer be
> > necessary once Will's patches land. Also noted here:
> > https://lkml.kernel.org/r/CANpmjNNw6M9Gqj6WGTHH4Cegu8roTVu5x6Vqs_tCBxX3gPwL4A@mail.gmail.com
> >
> > For reference, Will's series:
> > https://lore.kernel.org/lkml/20200421151537.19241-1-will@kernel.org/
>
> Right, good point. If that is going to get merged for the same release, we don't
> need my workarounds and I'll just keep them applied locally in my linux-next
> randconfig tree for the moment.
I'll send out a new version based on the kcsan stuff this week, so fingers
crossed for 5.8!
Will
prev parent reply other threads:[~2020-05-05 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 14:11 [PATCH] kcsan: fix section mismatch for __write_once_size/blacklisted_initcalls Arnd Bergmann
2020-05-05 14:17 ` Marco Elver
2020-05-05 15:05 ` Arnd Bergmann
2020-05-05 15:11 ` Will Deacon [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=20200505151150.GD24239@willie-the-truck \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mhiramat@kernel.org \
--cc=nivedita@alum.mit.edu \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).