From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] kmalloc_obj treewide refactor for v7.0-rc1
Date: Sat, 21 Feb 2026 14:37:46 -0800 [thread overview]
Message-ID: <202602211435.92647C06@keescook> (raw)
In-Reply-To: <CAHk-=wjS5=UuwcgxDWuLcRX5BbrO+=y9f8YQ+jJ6q7xs7U0gFQ@mail.gmail.com>
On Sat, Feb 21, 2026 at 12:16:57PM -0800, Linus Torvalds wrote:
> On Sat, 21 Feb 2026 at 11:49, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > So I've pulled this [..]
>
> Uhhuh. Something funky is going on.
>
> On my local build with clang and my local machine configuration, with
> this pull I get
Which Clang version?
> So there's something going on with this conversion, or there's another
> clang bug lurking.
>
> I'm not sure this is a fatal issue, but it makes me *very* nervous.
I'll see if I can reproduce this, but based on the last problem, I'm
going to assume it's the __builtin_counted_by_ref stuff again, as that's
the only "special" in in the kmalloc_flex() stuff...
--
Kees Cook
next prev parent reply other threads:[~2026-02-21 22:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 9:18 [GIT PULL] kmalloc_obj treewide refactor for v7.0-rc1 Kees Cook
2026-02-21 19:49 ` Linus Torvalds
2026-02-21 20:16 ` Linus Torvalds
2026-02-21 22:33 ` Linus Torvalds
2026-02-21 22:43 ` Kees Cook
2026-02-21 23:01 ` Linus Torvalds
2026-02-21 23:19 ` Linus Torvalds
2026-02-21 23:19 ` Kees Cook
2026-02-22 1:08 ` Eric Biggers
2026-02-22 14:50 ` David Laight
2026-02-22 17:34 ` Kees Cook
2026-02-23 9:19 ` Geert Uytterhoeven
2026-02-21 22:37 ` Kees Cook [this message]
2026-02-21 22:43 ` Linus Torvalds
2026-02-21 22:46 ` Kees Cook
2026-02-22 4:52 ` Linus Torvalds
2026-02-22 7:05 ` Kees Cook
2026-02-22 10:44 ` Julia Lawall
2026-02-22 17:37 ` Kees Cook
2026-02-22 10:38 ` David Laight
2026-02-21 19:55 ` pr-tracker-bot
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=202602211435.92647C06@keescook \
--to=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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