BPF List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Marco Elver <elver@google.com>,
	Alan Maguire <alan.maguire@oracle.com>,
	Kees Cook <kees@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Miguel Ojeda <ojeda@kernel.org>, Uros Bizjak <ubizjak@gmail.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Marc.Herbert@linux.intel.com, Heiko Carstens <hca@linux.ibm.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	namjain@linux.microsoft.com,
	"Paul E. McKenney" <paulmck@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrii Nakryiko <andrii.nakryiko@gmail.com>,
	Yonghong Song <yonghong.song@linux.dev>,
	Alexei Starovoitov <ast@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Eduard <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
	bvanassche <bvanassche@acm.org>,
	nilay@linux.ibm.com, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH] kcsan, compiler_types: avoid duplicate type issues in BPF Type Format
Date: Tue, 27 Jan 2026 17:04:01 -0800	[thread overview]
Message-ID: <20260127170401.43b972fa4f7b0b4419c7023c@linux-foundation.org> (raw)
In-Reply-To: <CAADnVQ+7ZxXE8O254rkYt+U9PO3Rxt681LaOT7W5UMj1PobHHA@mail.gmail.com>

On Tue, 27 Jan 2026 16:02:32 -0800 Alexei Starovoitov <alexei.starovoitov@gmail.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.

  reply	other threads:[~2026-01-28  1:04 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
2026-01-28  0:02       ` Alexei Starovoitov
2026-01-28  1:04         ` Andrew Morton [this message]
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=20260127170401.43b972fa4f7b0b4419c7023c@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Jason@zx2c4.com \
    --cc=Marc.Herbert@linux.intel.com \
    --cc=alan.maguire@oracle.com \
    --cc=alexei.starovoitov@gmail.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