From: Sasha Levin <sashal@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Rosen Penev <rosenp@gmail.com>, Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Florian Westphal <fw@strlen.de>, Julian Anastasov <ja@ssi.bg>,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] x86/csum: Relax the len and proto constraints in 32-bit csum_ipv6_magic()
Date: Mon, 19 Oct 2026 21:17:09 -0400 [thread overview]
Message-ID: <atbBFRU1Wm94oYB7@laps> (raw)
In-Reply-To: <20261020011140.GCata_zHOTeTXLdlr2@fat_crate.local>
On Mon, Oct 19, 2026 at 06:11:40PM -0700, Borislav Petkov wrote:
>> On Mon, Oct 19, 2026 at 5:32 PM Sasha Levin <sashal@kernel.org> wrote:
>> > KernelCI's kbuild-clang-21-i386-allmodconfig job has failed on mainline
>> > with this error since the 7.2 merge window, v7.3 included.
>
>This'll tell you how much people including us care about 32-bit...
I'm not stopping you from dropping it :)
>> Same as https://lore.kernel.org/all/20260904000833.2058186-1-rosenp@gmail.com/
>
>Except that Sasha's commit message explains it perfectly clear how this
>happens while for yours I would've asked how you're reproducing this.
>
>OTOH, I'm not sure I care about Sasha's AI's blurb about what params should've
>been in what registers and so on... :)
>
>If only you guys would agree on how to merge the two, assign authorship and
>drop the unnecessary blurb...
Any objection to just taking Rosen's? Maybe with the tags I had on mine to make
tracking easier?
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-10-20 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 0:32 Sasha Levin
2026-10-20 0:56 ` Rosen Penev
2026-10-20 1:11 ` Borislav Petkov
2026-10-20 1:17 ` Sasha Levin [this message]
2026-10-20 1:28 ` Borislav Petkov
2026-10-20 3:04 ` Rosen Penev
2026-10-20 17:25 ` Nick Desaulniers
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=atbBFRU1Wm94oYB7@laps \
--to=sashal@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fw@strlen.de \
--cc=hpa@zytor.com \
--cc=ja@ssi.bg \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=rosenp@gmail.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®