From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Dan Carpenter <error27@gmail.com>,
Matthew Wilcox <willy@infradead.org>, Kees Cook <kees@kernel.org>,
ksummit@lists.linux.dev
Subject: Re: [TECH TOPIC] Implementing malloc
Date: Fri, 10 Jul 2026 14:16:21 +0200 [thread overview]
Message-ID: <a3ce887f7d876c22f2a0048e6307fe75@perches.com> (raw)
In-Reply-To: <CAMuHMdUBHvY30ZuV=mpnkQ0Fip4vk0iqb252H9YNiOJ=AtPpyg@mail.gmail.com>
On 2026-07-10 13:21, Geert Uytterhoeven wrote:
> Hi Dan,
[]
> You know that most people are using the devm_*() allocators these
> days and so they do pass GFP_KERNEL? ;-)
One day they won't:
https://lore.kernel.org/lkml/eed0c57a2c897e34d411229c3de41c5402791894.1781575297.git.joe@perches.com/
prev parent reply other threads:[~2026-07-10 12:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 14:29 [TECH TOPIC] Implementing malloc Matthew Wilcox
2026-06-29 15:07 ` Dan Carpenter
2026-06-29 15:21 ` H. Peter Anvin
2026-06-29 15:31 ` Matthew Wilcox
2026-06-29 16:00 ` Vlastimil Babka (SUSE)
2026-06-29 16:37 ` H. Peter Anvin
2026-06-29 16:48 ` Alexey Dobriyan
2026-06-29 16:48 ` H. Peter Anvin
2026-06-29 18:19 ` Matthew Wilcox
2026-06-29 18:22 ` H. Peter Anvin
2026-06-29 18:29 ` Mark Brown
2026-06-29 18:37 ` Vlastimil Babka (SUSE)
2026-06-30 18:53 ` Steven Rostedt
2026-07-09 16:58 ` Kees Cook
2026-07-09 17:11 ` Matthew Wilcox
2026-07-09 17:30 ` H. Peter Anvin
2026-07-09 17:39 ` Greg KH
2026-07-09 17:42 ` Miguel Ojeda
2026-07-09 17:40 ` Miguel Ojeda
2026-07-09 18:18 ` H. Peter Anvin
2026-07-09 18:44 ` Miguel Ojeda
2026-07-09 18:50 ` H. Peter Anvin
2026-07-09 19:04 ` Miguel Ojeda
2026-07-09 18:42 ` Dan Carpenter
2026-07-09 18:45 ` Matthew Wilcox
2026-07-09 19:13 ` Linus Torvalds
2026-07-10 11:21 ` Geert Uytterhoeven
2026-07-10 11:44 ` Laurent Pinchart
2026-07-10 12:16 ` Joe Perches [this message]
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=a3ce887f7d876c22f2a0048e6307fe75@perches.com \
--to=joe@perches.com \
--cc=error27@gmail.com \
--cc=geert@linux-m68k.org \
--cc=kees@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.