linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Popple <apopple@nvidia.com>
To: Ralph Campbell <rcampbell@nvidia.com>
Cc: linux-mm@kvack.org, Felix Kuehling <felix.kuehling@amd.com>,
	Philip Yang <Philip.Yang@amd.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mm/hmm: fault non-owner device private entries
Date: Tue, 26 Jul 2022 11:26:40 +1000	[thread overview]
Message-ID: <87mtcwacg7.fsf@nvdebian.thelocal> (raw)
In-Reply-To: <20220725183615.4118795-2-rcampbell@nvidia.com>


Thanks Ralph, please add:

Reviewed-by: Alistair Popple <apopple@nvidia.com>

However I think the fixes tag is wrong, see below.

Ralph Campbell <rcampbell@nvidia.com> writes:

> If hmm_range_fault() is called with the HMM_PFN_REQ_FAULT flag and a
> device private PTE is found, the hmm_range::dev_private_owner page is
> used to determine if the device private page should not be faulted in.
> However, if the device private page is not owned by the caller,
> hmm_range_fault() returns an error instead of calling migrate_to_ram()
> to fault in the page.
>
> Cc: stable@vger.kernel.org
> Fixes: 76612d6ce4cc ("mm/hmm: reorganize how !pte_present is handled in hmm_vma_handle_pte()")

This should be 08ddddda667b ("mm/hmm: check the device private page owner in hmm_range_fault()")

> Signed-off-by: Ralph Campbell <rcampbell@nvidia.com>
> Reported-by: Felix Kuehling <felix.kuehling@amd.com>
> ---
>  mm/hmm.c | 19 ++++++++-----------
>  1 file changed, 8 insertions(+), 11 deletions(-)
>
> diff --git a/mm/hmm.c b/mm/hmm.c
> index 3fd3242c5e50..f2aa63b94d9b 100644
> --- a/mm/hmm.c
> +++ b/mm/hmm.c
> @@ -212,14 +212,6 @@ int hmm_vma_handle_pmd(struct mm_walk *walk, unsigned long addr,
>  		unsigned long end, unsigned long hmm_pfns[], pmd_t pmd);
>  #endif /* CONFIG_TRANSPARENT_HUGEPAGE */
>
> -static inline bool hmm_is_device_private_entry(struct hmm_range *range,
> -		swp_entry_t entry)
> -{
> -	return is_device_private_entry(entry) &&
> -		pfn_swap_entry_to_page(entry)->pgmap->owner ==
> -		range->dev_private_owner;
> -}
> -
>  static inline unsigned long pte_to_hmm_pfn_flags(struct hmm_range *range,
>  						 pte_t pte)
>  {
> @@ -252,10 +244,12 @@ static int hmm_vma_handle_pte(struct mm_walk *walk, unsigned long addr,
>  		swp_entry_t entry = pte_to_swp_entry(pte);
>
>  		/*
> -		 * Never fault in device private pages, but just report
> -		 * the PFN even if not present.
> +		 * Don't fault in device private pages owned by the caller,
> +		 * just report the PFN.
>  		 */
> -		if (hmm_is_device_private_entry(range, entry)) {
> +		if (is_device_private_entry(entry) &&
> +		    pfn_swap_entry_to_page(entry)->pgmap->owner ==
> +		    range->dev_private_owner) {
>  			cpu_flags = HMM_PFN_VALID;
>  			if (is_writable_device_private_entry(entry))
>  				cpu_flags |= HMM_PFN_WRITE;
> @@ -273,6 +267,9 @@ static int hmm_vma_handle_pte(struct mm_walk *walk, unsigned long addr,
>  		if (!non_swap_entry(entry))
>  			goto fault;
>
> +		if (is_device_private_entry(entry))
> +			goto fault;
> +
>  		if (is_device_exclusive_entry(entry))
>  			goto fault;


  reply	other threads:[~2022-07-26  1:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 18:36 [PATCH v2 0/2] " Ralph Campbell
2022-07-25 18:36 ` [PATCH v2 1/2] " Ralph Campbell
2022-07-26  1:26   ` Alistair Popple [this message]
2022-07-26 16:51     ` Ralph Campbell
2022-07-26 19:06       ` Andrew Morton
2022-07-26 20:59   ` John Hubbard
2022-07-25 18:36 ` [PATCH v2 2/2] mm/hmm: add a test for cross device private faults Ralph Campbell
2022-07-26  1:38   ` Alistair Popple
2022-07-26 21:03   ` John Hubbard
2022-07-26 21:14     ` Ralph Campbell

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=87mtcwacg7.fsf@nvdebian.thelocal \
    --to=apopple@nvidia.com \
    --cc=Philip.Yang@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=felix.kuehling@amd.com \
    --cc=jgg@nvidia.com \
    --cc=linux-mm@kvack.org \
    --cc=rcampbell@nvidia.com \
    --cc=stable@vger.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