From: David Hildenbrand <david@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, lpivarc@redhat.com
Subject: Re: [PATCH] vfio/type1: Unpin zero pages
Date: Tue, 30 Aug 2022 17:43:43 +0200 [thread overview]
Message-ID: <e1747d53-a02d-ca32-cdc4-702315da57df@redhat.com> (raw)
In-Reply-To: <20220830091110.3f6d1737.alex.williamson@redhat.com>
On 30.08.22 17:11, Alex Williamson wrote:
> On Tue, 30 Aug 2022 09:59:33 +0200
> David Hildenbrand <david@redhat.com> wrote:
>
>> On 30.08.22 05:05, Alex Williamson wrote:
>>> There's currently a reference count leak on the zero page. We increment
>>> the reference via pin_user_pages_remote(), but the page is later handled
>>> as an invalid/reserved page, therefore it's not accounted against the
>>> user and not unpinned by our put_pfn().
>>>
>>> Introducing special zero page handling in put_pfn() would resolve the
>>> leak, but without accounting of the zero page, a single user could
>>> still create enough mappings to generate a reference count overflow.
>>>
>>> The zero page is always resident, so for our purposes there's no reason
>>> to keep it pinned. Therefore, add a loop to walk pages returned from
>>> pin_user_pages_remote() and unpin any zero pages.
>>>
>>> Cc: David Hildenbrand <david@redhat.com>
>>> Cc: stable@vger.kernel.org
>>> Reported-by: Luboslav Pivarc <lpivarc@redhat.com>
>>> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
>>> ---
>>> drivers/vfio/vfio_iommu_type1.c | 12 ++++++++++++
>>> 1 file changed, 12 insertions(+)
>>>
>>> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
>>> index db516c90a977..8706482665d1 100644
>>> --- a/drivers/vfio/vfio_iommu_type1.c
>>> +++ b/drivers/vfio/vfio_iommu_type1.c
>>> @@ -558,6 +558,18 @@ static int vaddr_get_pfns(struct mm_struct *mm, unsigned long vaddr,
>>> ret = pin_user_pages_remote(mm, vaddr, npages, flags | FOLL_LONGTERM,
>>> pages, NULL, NULL);
>>> if (ret > 0) {
>>> + int i;
>>> +
>>> + /*
>>> + * The zero page is always resident, we don't need to pin it
>>> + * and it falls into our invalid/reserved test so we don't
>>> + * unpin in put_pfn(). Unpin all zero pages in the batch here.
>>> + */
>>> + for (i = 0 ; i < ret; i++) {
>>> + if (unlikely(is_zero_pfn(page_to_pfn(pages[i]))))
>>> + unpin_user_page(pages[i]);
>>> + }
>>> +
>>> *pfn = page_to_pfn(pages[0]);
>>> goto done;
>>> }
>>>
>>>
>>
>> As discussed offline, for the shared zeropage (that's not even
>> refcounted when mapped into a process), this makes perfect sense to me.
>>
>> Good question raised by Sean if ZONE_DEVICE pages might similarly be
>> problematic. But for them, we cannot simply always unpin here.
>
> What sort of VM mapping would give me ZONE_DEVICE pages? Thanks,
I think one approach is mmap'ing a devdax device. To test without actual
NVDIMM hardware, there are ways to simulate it even on bare metal using
the "memmap=" kernel parameter.
https://nvdimm.wiki.kernel.org/
Alternatively, you can use an emulated nvdimm device under QEMU -- but
then you'd have to run VFIO inside the VM. I know (that you know) that
there are ways to get that working, but it certainly requires more effort :)
... let me know if you need any tips&tricks.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-08-30 15:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 3:05 Alex Williamson
2022-08-30 5:34 ` Sean Christopherson
2022-08-30 7:59 ` David Hildenbrand
2022-08-30 15:11 ` Alex Williamson
2022-08-30 15:43 ` David Hildenbrand [this message]
2022-09-02 0:53 ` Jason Gunthorpe
2022-09-02 8:24 ` Tian, Kevin
2022-09-02 8:32 ` David Hildenbrand
2022-09-02 9:09 ` Tian, Kevin
2022-09-06 23:30 ` Jason Gunthorpe
2022-09-07 9:00 ` David Hildenbrand
2022-09-07 12:48 ` Jason Gunthorpe
2022-09-07 15:55 ` Alex Williamson
2022-09-07 16:40 ` Jason Gunthorpe
2022-09-07 18:56 ` Alex Williamson
2022-09-07 19:14 ` David Hildenbrand
2022-09-07 19:55 ` Jason Gunthorpe
2022-09-07 20:24 ` Alex Williamson
2022-09-07 23:07 ` Jason Gunthorpe
2022-09-08 1:10 ` Alex Williamson
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=e1747d53-a02d-ca32-cdc4-702315da57df@redhat.com \
--to=david@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpivarc@redhat.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
all inboxes | Powered by JetHome®