public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:46:01 -0800	[thread overview]
Message-ID: <202602211443.367DD24C6B@keescook> (raw)
In-Reply-To: <CAHk-=wjOeEk1oFekLvEx081ZROBm3oHTeWzOg8W5AFyErsC57A@mail.gmail.com>

On Sat, Feb 21, 2026 at 11:49:19AM -0800, Linus Torvalds wrote:
> IOW, how about doing something like this:
> 
>     #define pick_first(a, ...) a
>     #define GFP(...) pick_first(__VA_ARGS__ __VA_OPT__(,) GFP_KERNEL)
> 
>     #define kmalloc_obj(VAR_OR_TYPE, ...)                      \
>         __alloc_objs(kmalloc, GFP(__VA_ARGS__), typeof(VAR_OR_TYPE), 1)
> 
> and now you can just do
> 
>         a = kmalloc_obj(type);
> 
> if you just want the default GFP_KERNEL?

Yeah, I'd really like to do this, though I was trying to reduce the
macro shenanigans for this first phase, as you had correctly been
bothered about their proposed complexity. (And even their current
complexity is still creating problems for this series...) :|

-- 
Kees Cook

  parent reply	other threads:[~2026-02-21 22:46 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
2026-02-21 22:43       ` Linus Torvalds
2026-02-21 22:46   ` Kees Cook [this message]
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=202602211443.367DD24C6B@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