linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ashish Mhetre <amhetre@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>,
	Pranjal Shrivastava <praan@google.com>
Cc: robin.murphy@arm.com, joro@8bytes.org, will@kernel.org,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH RFC] iommu/dma: Validate page before accessing P2PDMA state
Date: Fri, 27 Feb 2026 11:16:02 +0530	[thread overview]
Message-ID: <58634d52-5d44-4ec9-b1f6-273b5c32b525@nvidia.com> (raw)
In-Reply-To: <20260226075806.GE12611@unreal>



On 2/26/2026 1:28 PM, Leon Romanovsky wrote:
> External email: Use caution opening links or attachments
>
>
> On Wed, Feb 25, 2026 at 08:11:29PM +0000, Pranjal Shrivastava wrote:
>> On Wed, Feb 25, 2026 at 09:56:09AM +0200, Leon Romanovsky wrote:
>>> On Wed, Feb 25, 2026 at 10:19:41AM +0530, Ashish Mhetre wrote:
>>>>
>>>> On 2/25/2026 2:27 AM, Pranjal Shrivastava wrote:
>>>>> External email: Use caution opening links or attachments
>>>>>
>>>>>
>>>>> On Tue, Feb 24, 2026 at 02:32:21PM +0200, Leon Romanovsky wrote:
>>>>>> On Tue, Feb 24, 2026 at 10:42:57AM +0000, Ashish Mhetre wrote:
>>>>>>> When mapping scatter-gather entries that reference reserved
>>>>>>> memory regions without struct page backing (e.g., bootloader created
>>>>>>> carveouts), is_pci_p2pdma_page() dereferences the page pointer
>>>>>>> returned by sg_page() without first verifying its validity.
>>>>>> I believe this behavior started after commit 88df6ab2f34b
>>>>>> ("mm: add folio_is_pci_p2pdma()"). Prior to that change, the
>>>>>> is_zone_device_page(page) check would return false when given a
>>>>>> non‑existent page pointer.
>>>>>>
>>>> Thanks Leon for the review. This crash started after commit 30280eee2db1
>>>> ("iommu/dma: support PCI P2PDMA pages in dma-iommu map_sg").
>>>>
>>>>> Doesn't folio_is_pci_p2pdma() also check for zone device?
>>>>> I see[1] that it does:
>>>>>
>>>>> static inline bool folio_is_pci_p2pdma(const struct folio *folio)
>>>>> {
>>>>>           return IS_ENABLED(CONFIG_PCI_P2PDMA) &&
>>>>>                   folio_is_zone_device(folio) &&
>>>>>                   folio->pgmap->type == MEMORY_DEVICE_PCI_P2PDMA;
>>>>> }
>>>>>
>>>>> I believe the problem arises due to the page_folio() call in
>>>>> folio_is_pci_p2pdma(page_folio(page)); within is_pci_p2pdma_page().
>>>>> page_folio() assumes it has a valid struct page to work with. For these
>>>>> carveouts, that isn't true.
>>>>>
>>>>> Potentially something like the following would stop the crash:
>>>>>
>>>>> diff --git a/include/linux/memremap.h b/include/linux/memremap.h
>>>>> index e3c2ccf872a8..e47876021afa 100644
>>>>> --- a/include/linux/memremap.h
>>>>> +++ b/include/linux/memremap.h
>>>>> @@ -197,7 +197,8 @@ static inline void folio_set_zone_device_data(struct folio *folio, void *data)
>>>>>
>>>>>    static inline bool is_pci_p2pdma_page(const struct page *page)
>>>>>    {
>>>>> -       return IS_ENABLED(CONFIG_PCI_P2PDMA) &&
>>>>> +       return IS_ENABLED(CONFIG_PCI_P2PDMA) && page &&
>>>>> +               pfn_valid(page_to_pfn(page)) &&
>>>>>                   folio_is_pci_p2pdma(page_folio(page));
>>>>>    }
>>>>>
>>>> Yes, this will also fix the crash.
>>>>
>>>>> But my broader question is: why are we calling a page-based API like
>>>>> is_pci_p2pdma_page() on non-struct-page memory in the first place?
>>>>> Could we instead add a helper to verify if the sg_page() return value
>>>>> is actually backed by a struct page? If it isn't, we should arguably
>>>>> skip the P2PDMA logic entirely and fall back to a dma_map_phys style
>>>>> path. Isn't handling these "pageless" physical ranges the primary reason
>>>>> dma_map_phys exists?
>>>> Thanks for the feedback, Pranjal.
>>>>
>>>> To clarify: are you suggesting we handle non-page-backed mappings inside
>>>> iommu_dma_map_sg (within dma-iommu), or that callers should detect
>>>> non-page-backed memory and use dma_map_phys instead of dma_map_sg?
>>> The latter one.
>>>
>> Yup, I meant the latter.
>>
>>>> Former approach sounds better so that existing iommu_dma_map_sg callers
>>>> don't need changes, but I'd like to confirm your preference.
>>> The bug is in callers which used wrong API, they need to be adapted.
>> Yes, the thing is, if the caller already knows that the region to be
>> mapped is NOT struct page-backed, then why does it use dma_map_sg
>> variants?
> Before dma_map_phys() was added, there was no reliable way to DMA‑map
> such memory, and using dma_map_sg() was a workaround that happened to
> work. I'm not sure whether it worked by design or by accident, but the
> correct approach now is to use dma_map_phys().

Thanks Leon and Pranjal for the detailed feedback. I'll update our 
callers to use
dma_map_phys() for non-page-backed buffers.

One question: would it make sense to add a check in iommu_dma_map_sg to
fail gracefully when non-page-backed buffers are passed, instead of crashing
the kernel?

Thanks,
Ashish Mhetre

> Thanks
>
>> Thanks
>> Praan



  reply	other threads:[~2026-02-27  5:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260224104257.1641429-1-amhetre@nvidia.com>
     [not found] ` <20260224123221.GM10607@unreal>
2026-02-24 20:57   ` Pranjal Shrivastava
2026-02-25  4:49     ` Ashish Mhetre
2026-02-25  7:56       ` Leon Romanovsky
2026-02-25 20:11         ` Pranjal Shrivastava
2026-02-26  7:58           ` Leon Romanovsky
2026-02-27  5:46             ` Ashish Mhetre [this message]
2026-02-25  7:50     ` Leon Romanovsky
2026-02-25 20:15       ` Pranjal Shrivastava

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=58634d52-5d44-4ec9-b1f6-273b5c32b525@nvidia.com \
    --to=amhetre@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=praan@google.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.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