From: Kees Cook <kees@kernel.org>
To: David Laight <david.laight.linux@gmail.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] kmalloc_obj treewide refactor for v7.0-rc1
Date: Sun, 22 Feb 2026 09:34:07 -0800 [thread overview]
Message-ID: <202602220930.65743CF@keescook> (raw)
In-Reply-To: <20260222145010.31580e59@pumpkin>
On Sun, Feb 22, 2026 at 02:50:10PM +0000, David Laight wrote:
> On Sat, 21 Feb 2026 17:08:47 -0800
> Eric Biggers <ebiggers@kernel.org> wrote:
>
> ...
> > It looks like the conversions of kmalloc() et al to kmalloc_flex() et al
> > were never in linux-next, so presumably that was a factor?
>
> Was the patch even posted to lkml?
> I don't remember seeing it.
The function was in next for the whole dev cycle, but the conversion
was huge, so I never sent it in email, but I've had a few snapshots on kernel.org
for 0day to pick up, for example:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=test/next-20260205/kmalloc_obj
--
Kees Cook
next prev parent reply other threads:[~2026-02-22 17:34 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 [this message]
2026-02-23 9:19 ` Geert Uytterhoeven
2026-02-21 22:37 ` Kees Cook
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=202602220930.65743CF@keescook \
--to=kees@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=ebiggers@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