[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20260127170401.43b972fa4f7b0b4419c7023c@linux-foundation.org>
Date: Tue, 27 Jan 2026 17:04:01 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Marco Elver <elver@...gle.com>, Alan Maguire <alan.maguire@...cle.com>,
Kees Cook <kees@...nel.org>, Nathan Chancellor <nathan@...nel.org>, Peter
Zijlstra <peterz@...radead.org>, Miguel Ojeda <ojeda@...nel.org>, Uros
Bizjak <ubizjak@...il.com>, "Jason A. Donenfeld" <Jason@...c4.com>,
Marc.Herbert@...ux.intel.com, Heiko Carstens <hca@...ux.ibm.com>,
"H. Peter Anvin" <hpa@...or.com>, namjain@...ux.microsoft.com,
"Paul E. McKenney" <paulmck@...nel.org>, LKML
<linux-kernel@...r.kernel.org>, Andrii Nakryiko
<andrii.nakryiko@...il.com>, Yonghong Song <yonghong.song@...ux.dev>,
Alexei Starovoitov <ast@...nel.org>, Jiri Olsa <jolsa@...nel.org>, Daniel
Borkmann <daniel@...earbox.net>, Martin KaFai Lau <martin.lau@...ux.dev>,
Eduard <eddyz87@...il.com>, Song Liu <song@...nel.org>, John Fastabend
<john.fastabend@...il.com>, KP Singh <kpsingh@...nel.org>, Stanislav
Fomichev <sdf@...ichev.me>, Hao Luo <haoluo@...gle.com>, bvanassche
<bvanassche@....org>, nilay@...ux.ibm.com, bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH] kcsan, compiler_types: avoid duplicate type issues in
BPF Type Format
On Tue, 27 Jan 2026 16:02:32 -0800 Alexei Starovoitov <alexei.starovoitov@...il.com> wrote:
> > 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.
>
> You mean in the upcoming merge window, right?
Yes.
It could be added to 6.19-rcX/-stable if there's a need?
> The severity of the bug is significant. Better to land it sooner
> rather than later.
OK, that wasn't clear to me from the changelog.
> > It's unclear whether a -stable backport is required. Thoughts on this
> > are sought.
>
> Yes, since without it kcsan and bpf are mutually exclusive.
OK, cc:stable added.
Powered by blists - more mailing lists