From: Andrew Morton <akpm@linux-foundation.org>
To: Marco Elver <elver@google.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
kees@kernel.org, nathan@kernel.org, peterz@infradead.org,
ojeda@kernel.org, ubizjak@gmail.com, Jason@zx2c4.com,
Marc.Herbert@linux.intel.com, hca@linux.ibm.com, hpa@zytor.com,
namjain@linux.microsoft.com, paulmck@kernel.org,
linux-kernel@vger.kernel.org, andrii.nakryiko@gmail.com,
yonghong.song@linux.dev, ast@kernel.org, jolsa@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, bvanassche@acm.org,
nilay@linux.ibm.com, bpf@vger.kernel.org
Subject: Re: [PATCH] kcsan, compiler_types: avoid duplicate type issues in BPF Type Format
Date: Tue, 27 Jan 2026 15:31:29 -0800 [thread overview]
Message-ID: <20260127153129.2ca728a4550375a4172e1351@linux-foundation.org> (raw)
In-Reply-To: <CANpmjNNoDHQOfH+bUqjpHdzYDxLwG7wA9qEywfWFNamt66Ziyg@mail.gmail.com>
On Wed, 28 Jan 2026 00:08:10 +0100 Marco Elver <elver@google.com> wrote:
> > "KCSAN and KCSAN_SANITIZE objects" doesn't make sense.
> > "KCSAN_SANITIZE.. := n" objects?
> > Or just "instrumented and uninstrumented source files".
> > Anyway, I know what you mean, but others might not. :-)
> >
> > > Fixes: 31f605a308e6 ("kcsan, compiler_types: Introduce __data_racy type qualifier")
> > > Reported-by: Nilay Shroff <nilay@linux.ibm.com>
> > > Suggested-by: Marco Elver <elver@google.com>
> > > Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
> >
> > Reviewed-by: Marco Elver <elver@google.com>
>
> Which tree do compiler_types.h changes go through these days?
Thanks for poking.
compiler_types.h appears to be a free-for-all. It's best to view such
a thing as a KCSAN patch rather than a compiler_types.h patch - that
the patch affects compiler_types.h is incidental.
31f605a308e6 came in via paulmck so convention (which perhaps only I
maintain) says "Paul", but whatever - getting the fix merged is the
important part.
So I'll grab Alan's patch, shall drop if it pops up in -next via a
different route. Aiming for upstreaming in the next merge window.
It's unclear whether a -stable backport is required. Thoughts on this
are sought.
next prev parent reply other threads:[~2026-01-27 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 9:17 [PATCH] kcsan, compiler_types: avoid duplicate type issues in BPF Type Format Alan Maguire
2026-01-16 10:13 ` Marco Elver
2026-01-27 23:08 ` Marco Elver
2026-01-27 23:31 ` Andrew Morton [this message]
2026-01-28 0:02 ` Alexei Starovoitov
2026-01-28 1:04 ` Andrew Morton
2026-01-28 1:44 ` Marco Elver
2026-01-16 13:15 ` Nilay Shroff
2026-01-16 17:26 ` Yonghong Song
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=20260127153129.2ca728a4550375a4172e1351@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Jason@zx2c4.com \
--cc=Marc.Herbert@linux.intel.com \
--cc=alan.maguire@oracle.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=bvanassche@acm.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=elver@google.com \
--cc=haoluo@google.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kees@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=namjain@linux.microsoft.com \
--cc=nathan@kernel.org \
--cc=nilay@linux.ibm.com \
--cc=ojeda@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=ubizjak@gmail.com \
--cc=yonghong.song@linux.dev \
/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