From: Hugh Dickins <hughd@google.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: Hugh Dickins <hughd@google.com>,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@redhat.com>,
Vivek Kasireddy <vivek.kasireddy@intel.com>,
baolin.wang@linux.alibaba.com, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
syzbot+f64019ba229e3a5c411b@syzkaller.appspotmail.com
Subject: Re: [PATCH] mm/memfd: clear hugetlb pages on allocation
Date: Tue, 11 Nov 2025 23:55:17 -0800 (PST) [thread overview]
Message-ID: <a6d0156b-5f65-9426-f27f-8a1af59bffa0@google.com> (raw)
In-Reply-To: <CADhLXY4qMvBTqirNmzgiPszn8vCkCFV6GGeDkNpxVDi32uhzEw@mail.gmail.com>
On Wed, 12 Nov 2025, Deepanshu Kartikey wrote:
> Hi Hugh,
>
> Thank you for the quick review and for looping in the hugetlb maintainers!
>
> You raise good points about the approach. I chose explicit zeroing in
> memfd_alloc_folio() because hugetlb_reserve_pages() can allocate pages
> without seeing the __GFP_ZERO flag, but I'm happy to revise if the
> hugetlb maintainers prefer a different approach.
>
> I'll add the Fixes: 89c1905d9c14 tag and Cc: stable in v2.
>
> Should I send v2 now with just the tag added, or wait for feedback from
> Muchun/Oscar/David on the overall approach first?
No need for a v2 at this stage - Andrew is very much more than capable
of adding in that Fixes tag and Cc stable if he's inclined to grab your
patch for mm.git in the interim, but let's wait to hear from hugetlb
folks before finalizing (I expect they'll say __GFP_ZERO is no good).
Hugh
next prev parent reply other threads:[~2025-11-12 7:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 3:16 Deepanshu Kartikey
2025-11-12 6:55 ` Hugh Dickins
2025-11-12 7:28 ` Deepanshu Kartikey
2025-11-12 7:55 ` Hugh Dickins [this message]
2025-11-12 9:13 ` Oscar Salvador
2025-11-12 9:26 ` Deepanshu Kartikey
2025-11-12 10:09 ` David Hildenbrand (Red Hat)
2025-11-12 11:56 ` Oscar Salvador
2025-11-12 12:06 ` Deepanshu Kartikey
2025-11-12 14:54 ` Deepanshu Kartikey
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=a6d0156b-5f65-9426-f27f-8a1af59bffa0@google.com \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=syzbot+f64019ba229e3a5c411b@syzkaller.appspotmail.com \
--cc=vivek.kasireddy@intel.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