vfio/type1: check pfn valid before converting to struct page
Subsystems (2)
PATCH v2 1/1 vfio/type1: check pfn valid before converting to struct page
Check physical PFN is valid before converting the PFN to a struct page pointer to be returned to caller of vfio_pin_pages().
vfio_pin_pages() pins user pages with contiguous IOVA.
If the IOVA of a user page to be pinned belongs to vma of vm_flags VM_PFNMAP, pin_user_pages_remote() will return -EFAULT without returning struct page address for this PFN. This is because usually this kind of PFN (e.g. MMIO PFN) has no valid struct page address associated. Upon this error, vaddr_get_pfns() will obtain the physical PFN directly.
While previously vfio_pin_pages() returns to caller PFN arrays directly, after commit34a255e67615 ("vfio: Replace phys_pfn with pages for vfio_pin_pages()"), PFNs will be converted to "struct page *" unconditionally and therefore the returned "struct page *" array may contain invalid struct page addresses.
Given current in-tree users of vfio_pin_pages() only expect "struct page * returned, check PFN validity and return -EINVAL to let the caller be aware of IOVAs to be pinned containing PFN not able to be returned in "struct page *" array. So that, the caller will not consume the returned pointer (e.g. test PageReserved()) and avoid error like "supervisor read access in kernel mode".
---
v2: update commit message to explain background/problem clearly. (Sean)
--- drivers/vfio/vfio_iommu_type1.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/vfio/vfio_iommu_type1.c +5 -0
@@ -860,6 +860,11 @@ static int vfio_iommu_type1_pin_pages(void *iommu_data,if (ret) goto pin_unwind; +if (!pfn_valid (phys_pfn)) { + ret = -EINVAL ; + goto pin_unwind; + } + ret =vfio_add_to_pfn_list (dma, iova, phys_pfn);if (ret) {if (put_pfn (phys_pfn, dma->prot) && do_accounting)
base-commit: b3c98052d46948a8d65d2778c7f306ff38366aac
Signature · 1 line
2.17.1
Quoted 24 lines · Yan Zhao
Check physical PFN is valid before converting the PFN to a struct page pointer to be returned to caller of
vfio_pin_pages().
vfio_pin_pages()pins user pages with contiguous IOVA.
If the IOVA of a user page to be pinned belongs to vma ofvm_flagsVM_PFNMAP,pin_user_pages_remote()will return-EFAULTwithout returning struct page address for this PFN. This is because usually this kind of PFN (e.g. MMIO PFN) has no valid struct page address associated. Upon this error,vaddr_get_pfns()will obtain the physical PFN directly.While previously
vfio_pin_pages()returns to caller PFN arrays directly, after commit34a255e67615("vfio: Replacephys_pfnwith pages forvfio_pin_pages()"), PFNs will be converted to "struct page *" unconditionally and therefore the returned "struct page *" array may contain invalid struct page addresses.Given current in-tree users of
vfio_pin_pages()only expect "struct page * returned, check PFN validity and return-EINVALto let the caller be aware of IOVAs to be pinned containing PFN not able to be returned in "struct page *" array. So that, the caller will not consume the returned pointer (e.g. testPageReserved()) and avoid error like "supervisor read access in kernel mode".
Quoted 4 lines
Fixes 34a255e67615 ("vfio: Replace phys_pfn with pages for vfio_pin_pages()")Cc Sean Christopherson <[email protected]>Reviewed-by Jason Gunthorpe <[email protected]>Signed-off-by Yan Zhao <[email protected]>
Quoted 40 lines · On Fri, 19 May 2023 14:58:43 +0800 Yan Zhao <[email protected]> wrote:
Check physical PFN is valid before converting the PFN to a struct page pointer to be returned to caller of
vfio_pin_pages().
vfio_pin_pages()pins user pages with contiguous IOVA.
If the IOVA of a user page to be pinned belongs to vma ofvm_flagsVM_PFNMAP,pin_user_pages_remote()will return-EFAULTwithout returning struct page address for this PFN. This is because usually this kind of PFN (e.g. MMIO PFN) has no valid struct page address associated. Upon this error,vaddr_get_pfns()will obtain the physical PFN directly.While previously
vfio_pin_pages()returns to caller PFN arrays directly, after commit34a255e67615("vfio: Replacephys_pfnwith pages forvfio_pin_pages()"), PFNs will be converted to "struct page *" unconditionally and therefore the returned "struct page *" array may contain invalid struct page addresses.Given current in-tree users of
vfio_pin_pages()only expect "struct page * returned, check PFN validity and return-EINVALto let the caller be aware of IOVAs to be pinned containing PFN not able to be returned in "struct page *" array. So that, the caller will not consume the returned pointer (e.g. testPageReserved()) and avoid error like "supervisor read access in kernel mode".Fixes 34a255e67615 ("vfio: Replace phys_pfn with pages for vfio_pin_pages()")Cc Sean Christopherson <[email protected]>Reviewed-by Jason Gunthorpe <[email protected]>Signed-off-by Yan Zhao <[email protected]>---
v2: update commit message to explain background/problem clearly. (Sean)--- drivers/vfio/vfio_iommu_type1.c | 5 +++++ 1 file changed, 5 insertions(+)drivers/vfio/vfio_iommu_type1.c +0
-0
drivers/vfio/vfio_iommu_type1.c static int vfio_iommu_type1_pin_pages(void *iommu_data, · line 863
Quoted 4 lines
drivers/vfio/vfio_iommu_type1.c +1
-0@@ -860,6 +860,11 @@ static int vfio_iommu_type1_pin_pages(void *iommu_data,if (ret) goto pin_unwind; +if (!pfn_valid (phys_pfn)) {
Why wouldn't we use our is_invalid_reserved_pfn() test here? Doing so would also make it more consistent why we don't need to call put_pfn() or rewind accounting for this page. Thanks,
Alex
Quoted 9 lines
drivers/vfio/vfio_iommu_type1.c +4
-0+ ret = -EINVAL ; + goto pin_unwind; + } + ret =vfio_add_to_pfn_list (dma, iova, phys_pfn);if (ret) {if (put_pfn (phys_pfn, dma->prot) && do_accounting)base-commit:
b3c98052d46948a8d65d2778c7f306ff38366aac
Quoted 46 lines · Alex Williamson
Quoted 43 lines · On Fri, 19 May 2023 14:58:43 +0800 Yan Zhao <[email protected]> wrote:
Check physical PFN is valid before converting the PFN to a struct page pointer to be returned to caller of
vfio_pin_pages().
vfio_pin_pages()pins user pages with contiguous IOVA.
If the IOVA of a user page to be pinned belongs to vma ofvm_flagsVM_PFNMAP,pin_user_pages_remote()will return-EFAULTwithout returning struct page address for this PFN. This is because usually this kind of PFN (e.g. MMIO PFN) has no valid struct page address associated. Upon this error,vaddr_get_pfns()will obtain the physical PFN directly.While previously
vfio_pin_pages()returns to caller PFN arrays directly, after commit34a255e67615("vfio: Replacephys_pfnwith pages forvfio_pin_pages()"), PFNs will be converted to "struct page *" unconditionally and therefore the returned "struct page *" array may contain invalid struct page addresses.Given current in-tree users of
vfio_pin_pages()only expect "struct page * returned, check PFN validity and return-EINVALto let the caller be aware of IOVAs to be pinned containing PFN not able to be returned in "struct page *" array. So that, the caller will not consume the returned pointer (e.g. testPageReserved()) and avoid error like "supervisor read access in kernel mode".Fixes 34a255e67615 ("vfio: Replace phys_pfn with pages for vfio_pin_pages()")Cc Sean Christopherson <[email protected]>Reviewed-by Jason Gunthorpe <[email protected]>Signed-off-by Yan Zhao <[email protected]>---
v2: update commit message to explain background/problem clearly. (Sean)--- drivers/vfio/vfio_iommu_type1.c | 5 +++++ 1 file changed, 5 insertions(+)drivers/vfio/vfio_iommu_type1.c +0
-0@@ -860,6 +860,11 @@ static int vfio_iommu_type1_pin_pages(void *iommu_data,if (ret) goto pin_unwind;
Quoted 6 lines
drivers/vfio/vfio_iommu_type1.c static int vfio_iommu_type1_pin_pages(void *iommu_data, · line 863
Quoted 1 line
drivers/vfio/vfio_iommu_type1.c +1
-0+if (!pfn_valid (phys_pfn)) {Why wouldn't we use our
is_invalid_reserved_pfn()test here? Doing so would also make it more consistent why we don't need to callput_pfn()or rewind accounting for this page. Thanks,
I actually struggled in choosing is_invalid_reserved_pfn() or pfn_valid() when writing this patch.
Choosing pfn_valid() is because invalid PFN obviously cannot have struct page address and it's a bug fix.
While declining reserved pages will have the IOVA range supported by vfio_pin_pages() even more reduced. So I don't know if there's enough justification to do so, given that (1) device zone memory usually has PG_reserved set. (2) vm_normal_page() also contains reserved page.
Thanks
Yan
Quoted 11 lines
Quoted 10 lines
drivers/vfio/vfio_iommu_type1.c +4
-0+ ret = -EINVAL ; + goto pin_unwind; + } + ret =vfio_add_to_pfn_list (dma, iova, phys_pfn);if (ret) {if (put_pfn (phys_pfn, dma->prot) && do_accounting)base-commit:
b3c98052d46948a8d65d2778c7f306ff38366aac
Quoted 56 lines · On Tue, 23 May 2023 13:48:22 +0800 Yan Zhao <[email protected]> wrote:
Quoted 46 lines · Alex Williamson
Quoted 43 lines · On Fri, 19 May 2023 14:58:43 +0800 Yan Zhao <[email protected]> wrote:
Check physical PFN is valid before converting the PFN to a struct page pointer to be returned to caller of
vfio_pin_pages().
vfio_pin_pages()pins user pages with contiguous IOVA.
If the IOVA of a user page to be pinned belongs to vma ofvm_flagsVM_PFNMAP,pin_user_pages_remote()will return-EFAULTwithout returning struct page address for this PFN. This is because usually this kind of PFN (e.g. MMIO PFN) has no valid struct page address associated. Upon this error,vaddr_get_pfns()will obtain the physical PFN directly.While previously
vfio_pin_pages()returns to caller PFN arrays directly, after commit34a255e67615("vfio: Replacephys_pfnwith pages forvfio_pin_pages()"), PFNs will be converted to "struct page *" unconditionally and therefore the returned "struct page *" array may contain invalid struct page addresses.Given current in-tree users of
vfio_pin_pages()only expect "struct page * returned, check PFN validity and return-EINVALto let the caller be aware of IOVAs to be pinned containing PFN not able to be returned in "struct page *" array. So that, the caller will not consume the returned pointer (e.g. testPageReserved()) and avoid error like "supervisor read access in kernel mode".Fixes 34a255e67615 ("vfio: Replace phys_pfn with pages for vfio_pin_pages()")Cc Sean Christopherson <[email protected]>Reviewed-by Jason Gunthorpe <[email protected]>Signed-off-by Yan Zhao <[email protected]>---
v2: update commit message to explain background/problem clearly. (Sean)--- drivers/vfio/vfio_iommu_type1.c | 5 +++++ 1 file changed, 5 insertions(+)drivers/vfio/vfio_iommu_type1.c +0
-0@@ -860,6 +860,11 @@ static int vfio_iommu_type1_pin_pages(void *iommu_data,if (ret) goto pin_unwind;Quoted 6 lines
drivers/vfio/vfio_iommu_type1.c static int vfio_iommu_type1_pin_pages(void *iommu_data, · line 863
Quoted 1 line
drivers/vfio/vfio_iommu_type1.c +1
-0+if (!pfn_valid (phys_pfn)) {Why wouldn't we use our
is_invalid_reserved_pfn()test here? Doing so would also make it more consistent why we don't need to callput_pfn()or rewind accounting for this page. Thanks,I actually struggled in choosing
is_invalid_reserved_pfn()orpfn_valid()when writing this patch.
Quoted 7 lines
Choosing
pfn_valid()is because invalid PFN obviously cannot have struct page address and it's a bug fix.While declining reserved pages will have the IOVA range supported by
vfio_pin_pages()even more reduced. So I don't know if there's enough justification to do so, given that (1) device zone memory usually hasPG_reservedset. (2)vm_normal_page()also contains reserved page.
Based on the exclusion we have in vaddr_get_pfn() where we unpin zero-page pfns because they hit on the is_invalid_reserved_pfn() test and break our accounting otherwise, this does seem like the correct choice. I can imagine a scenario where the device wants to do a DMA read from VM memory backed by the zero page. Ok. Thanks,
Alex
Alex Williamson
AppliedQuoted 52 lines · On Fri, 19 May 2023 14:58:43 +0800 Yan Zhao <[email protected]> wrote:
Check physical PFN is valid before converting the PFN to a struct page pointer to be returned to caller of
vfio_pin_pages().
vfio_pin_pages()pins user pages with contiguous IOVA.
If the IOVA of a user page to be pinned belongs to vma ofvm_flagsVM_PFNMAP,pin_user_pages_remote()will return-EFAULTwithout returning struct page address for this PFN. This is because usually this kind of PFN (e.g. MMIO PFN) has no valid struct page address associated. Upon this error,vaddr_get_pfns()will obtain the physical PFN directly.While previously
vfio_pin_pages()returns to caller PFN arrays directly, after commit34a255e67615("vfio: Replacephys_pfnwith pages forvfio_pin_pages()"), PFNs will be converted to "struct page *" unconditionally and therefore the returned "struct page *" array may contain invalid struct page addresses.Given current in-tree users of
vfio_pin_pages()only expect "struct page * returned, check PFN validity and return-EINVALto let the caller be aware of IOVAs to be pinned containing PFN not able to be returned in "struct page *" array. So that, the caller will not consume the returned pointer (e.g. testPageReserved()) and avoid error like "supervisor read access in kernel mode".Fixes 34a255e67615 ("vfio: Replace phys_pfn with pages for vfio_pin_pages()")Cc Sean Christopherson <[email protected]>Reviewed-by Jason Gunthorpe <[email protected]>Signed-off-by Yan Zhao <[email protected]>---
v2: update commit message to explain background/problem clearly. (Sean)--- drivers/vfio/vfio_iommu_type1.c | 5 +++++ 1 file changed, 5 insertions(+)drivers/vfio/vfio_iommu_type1.c +5
-0@@ -860,6 +860,11 @@ static int vfio_iommu_type1_pin_pages(void *iommu_data,if (ret) goto pin_unwind; +if (!pfn_valid (phys_pfn)) { + ret = -EINVAL ; + goto pin_unwind; + } + ret =vfio_add_to_pfn_list (dma, iova, phys_pfn);if (ret) {if (put_pfn (phys_pfn, dma->prot) && do_accounting)
Quoted 1 line
base-commit:
b3c98052d46948a8d65d2778c7f306ff38366aac
Applied to vfio for-linus branch for v6.4. Thanks!
Alex