From: Steven Sistare <steven.sistare@oracle.com>
To: "Kasireddy, Vivek" <vivek.kasireddy@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Peter Xu <peterx@redhat.com>,
David Hildenbrand <david@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [PATCH V1 0/5] memfd-pin huge page fixes
Date: Wed, 4 Sep 2024 10:51:49 -0400 [thread overview]
Message-ID: <4ffa7e8e-4fad-438a-a021-aaddf5ce3e0f@oracle.com> (raw)
In-Reply-To: <IA0PR11MB7185092EFD8CEC24CE38DB1DF89C2@IA0PR11MB7185.namprd11.prod.outlook.com>
On 9/3/2024 9:12 PM, Kasireddy, Vivek wrote:
> Hi Steve,
>
>> Subject: [PATCH V1 0/5] memfd-pin huge page fixes
>>
>> Fix multiple bugs that occur when using memfd_pin_folios with hugetlb
>> pages
>> and THP. The hugetlb bugs only bite when the page is not yet faulted in
>> when memfd_pin_folios is called. The THP bug bites when the starting offset
>> passed to memfd_pin_folios is not huge page aligned. See the commit
>> messages
>> for details.
> Thank you for fixing these bugs. I have Acked all patches except for patch #1,
> as my understanding of xarrays is limited at this point.
>
> Also, could you please briefly describe how you have exercised memfd_alloc_folio()
> code path or what tests you have run to uncover these bugs? I'd like to
> figure out ways to augment the list of udmabuf tests to validate scenarios
> where hugetlb pages are not faulted in and memfd_pin_folios() is called.
I am extending iommufd to support memfd pinning, so I added a new ioctl which
takes an fd, offset, and length to pin. I am just getting started, so currently
it does nothing more than call memfd_pin_folios immediately followed by unpin_folios.
Then exit the process. That is sufficient to trigger all the bugs except the alloc
race panic. I tested with these files:
/dev/hugepages/file
/dev/shm/file with: mount -o remount,huge=always /dev/shm
memfd_create(MFD_HUGETLB)
memfd_create(0) with: echo always > /sys/kernel/mm/transparent_hugepage/shmem_enabled
- Steve
>> Steve Sistare (5):
>> mm/filemap: fix filemap_get_folios_contig THP panic
>> mm/hugetlb: fix memfd_pin_folios free_huge_pages leak
>> mm/hugetlb: fix memfd_pin_folios resv_huge_pages leak
>> mm/gup: fix memfd_pin_folios hugetlb page allocation
>> mm/gup: fix memfd_pin_folios alloc race panic
>>
>> include/linux/hugetlb.h | 10 ++++++++++
>> mm/filemap.c | 4 ++++
>> mm/gup.c | 5 ++++-
>> mm/hugetlb.c | 17 +++++++++++++++++
>> mm/memfd.c | 15 +++++++++------
>> 5 files changed, 44 insertions(+), 7 deletions(-)
>>
>> --
>> 1.8.3.1
>
next prev parent reply other threads:[~2024-09-04 14:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 14:25 Steve Sistare
2024-09-03 14:25 ` [PATCH V1 1/5] mm/filemap: fix filemap_get_folios_contig THP panic Steve Sistare
2024-09-03 14:25 ` [PATCH V1 2/5] mm/hugetlb: fix memfd_pin_folios free_huge_pages leak Steve Sistare
2024-09-04 0:45 ` Kasireddy, Vivek
2024-09-04 14:52 ` Steven Sistare
2024-09-03 14:25 ` [PATCH V1 3/5] mm/hugetlb: fix memfd_pin_folios resv_huge_pages leak Steve Sistare
2024-09-04 1:04 ` Kasireddy, Vivek
2024-09-04 14:52 ` Steven Sistare
2024-09-03 14:25 ` [PATCH V1 4/5] mm/gup: fix memfd_pin_folios hugetlb page allocation Steve Sistare
2024-09-04 1:06 ` Kasireddy, Vivek
2024-09-04 14:51 ` Steven Sistare
2024-09-03 14:25 ` [PATCH V1 5/5] mm/gup: fix memfd_pin_folios alloc race panic Steve Sistare
2024-09-04 1:07 ` Kasireddy, Vivek
2024-09-04 1:12 ` [PATCH V1 0/5] memfd-pin huge page fixes Kasireddy, Vivek
2024-09-04 14:51 ` Steven Sistare [this message]
2024-09-06 8:09 ` Kasireddy, Vivek
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=4ffa7e8e-4fad-438a-a021-aaddf5ce3e0f@oracle.com \
--to=steven.sistare@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jgg@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=peterx@redhat.com \
--cc=vivek.kasireddy@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox