From: Mike Rapoport <rppt@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Mahad Ibrahim <mahad.ibrahim.dev@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lkdtm: use kmalloc() instead of __get_free_page
Date: Sun, 26 Jul 2026 10:02:53 +0300 [thread overview]
Message-ID: <amWxHSl76OD1fKQW@kernel.org> (raw)
In-Reply-To: <202607222046.D287828@keescook>
Hi Kees,
On Wed, Jul 22, 2026 at 08:47:01PM -0700, Kees Cook wrote:
> On Wed, Jul 22, 2026 at 11:42:25PM +0000, Mahad Ibrahim wrote:
> > For context, this is part of the broader __get_free_page() -> kmalloc()
> > transition Mike Rapoport is performing. I noticed it on the mailing
> > lists and found this site which wasn't covered.
> >
> > Some background:
> >
> > [1] https://lore.kernel.org/all/CA+55aFwp4iy4rtX2gE2WjBGFL=NxMVnoFeHqYa2j1dYOMMGqxg@mail.gmail.com/
> > [2] https://lore.kernel.org/linux-scsi/20260704-b4-scsi-v2-0-7d2d21a810de@kernel.org/T/#t
> >
> > I apologize for this messy reply. I thought I had added the context, but
> > I didn't.
>
> Do you want this to land via my tree or via the series Mike is doing?
I'm not actually maintaining a tree for this, I'm sending patches to the
subsystem maintainers, so your tree would be great.
> --
> Kees Cook
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-07-26 7:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 23:02 [PATCH] lkdtm: use kmalloc() instead of __get_free_page Mahad Ibrahim
2026-07-22 23:42 ` Mahad Ibrahim
2026-07-23 3:47 ` Kees Cook
2026-07-24 9:51 ` Mahad Ibrahim
2026-07-26 7:02 ` Mike Rapoport [this message]
2026-07-23 8:45 ` David Laight
2026-07-23 9:00 ` Arnd Bergmann
2026-07-24 10:29 ` Mahad Ibrahim
2026-07-26 7:06 ` Mike Rapoport
2026-07-26 7:03 ` Mike Rapoport
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=amWxHSl76OD1fKQW@kernel.org \
--to=rppt@kernel.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mahad.ibrahim.dev@gmail.com \
/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