From: "Paul E. McKenney" <paulmck@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Marco Elver <elver@google.com>, Arnd Bergmann <arnd@kernel.org>,
Kees Cook <keescook@chromium.org>,
Dmitry Vyukov <dvyukov@google.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Miroslav Benes <mbenes@suse.cz>,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kcsan: select CONFIG_CONSTRUCTORS
Date: Wed, 15 Feb 2023 14:42:18 -0800 [thread overview]
Message-ID: <20230215224218.GN2948950@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <78b2ed7d-2585-479f-98b1-ed2574a64cb8@app.fastmail.com>
On Wed, Feb 15, 2023 at 10:48:11AM +0100, Arnd Bergmann wrote:
> On Wed, Feb 15, 2023, at 10:25, Marco Elver wrote:
> > On Wed, 15 Feb 2023 at 10:15, Arnd Bergmann <arnd@kernel.org> wrote:
>
> > Looks like KASAN does select CONSTRUCTORS already, so KCSAN should as well.
> >
> > Do you have a tree to take this through, or should it go through -rcu
> > as usual for KCSAN patches?
>
> I don't have a tree for taking these build fixes, so it would be good if you could forward it as appropriate.
Queued and pushed, thank you both!
Is this ready for the upcoming merge window, or would you rather that
I hold off until the v6.4 merge window? (I am tempted to treat this
as a bug fix, thus sending it earlier rather than later, but figured I
should ask.)
Thanx, Paul
next prev parent reply other threads:[~2023-02-15 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 9:14 [PATCH] kcsan: select CONFIG_CONSTRUCTORS Arnd Bergmann
2023-02-15 9:25 ` Marco Elver
2023-02-15 9:48 ` Arnd Bergmann
2023-02-15 22:42 ` Paul E. McKenney [this message]
2023-02-16 7:00 ` Marco Elver
2023-02-16 18:36 ` Paul E. McKenney
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=20230215224218.GN2948950@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=jpoimboe@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=peterz@infradead.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).