linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Boone, Max" <mboone@akamai.com>
To: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	"Vlastimil Babka" <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	"Suren Baghdasaryan" <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] mm/pagewalk: fix race between concurrent split and refault
Date: Wed, 18 Mar 2026 13:08:33 +0000	[thread overview]
Message-ID: <719CB417-F511-402A-91E3-8A696ABCE0D5@akamai.com> (raw)
In-Reply-To: <7ded426a-0cb5-437b-9634-8d806b704db6@lucifer.local>

[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]


> On Mar 18, 2026, at 1:55 PM, Lorenzo Stoakes (Oracle) <ljs@kernel.org> wrote:
> 
>> […]
> 
> So IOW, the PUD entry is split, then refaulted back to a PUD leaf entry
> again?

As far as I understand indeed, although the usage and faulting of huge
pfnmaps does not feel intuitive to me yet. Empirically, yes, observing this
when follow_fault_pfn() in drivers/vfio/vfio_iommu_type1.c is running 
concurrently with walk_pud_range(). I have another patch sent up to
that list because this fix causes follow_fault_pfn() to return -EINVAL [1].

>> […] 
> 
> I think it mirrors the retry logic in walk_pte_range() more closely right?
> Because there it's:
> 
> if (!pte)
> walk->action = ACTION_AGAIN;
> return err;
> 
> I.e. let the parent handle the PTE not being got by pte_offset_map_lock(),
> and you draw a comparison to this in the comment in walk_pmd_range().

I’d personally say that the main logic introduced is walk_pud_range() retrying when
walk_pmd_range() fails. We’re also splitting the PUD in walk_pud_range() and 
descending. But yeah, retry logic mirrors walk_pmd_range(), deciding that we need
to retry mirrors walk_pte_range().

> 
>> 
>> Fixes: a00cc7d9dd93 ("mm, x86: add support for PUD-sized transparent hugepages")
> 
> Yikes, really? :) This is from 2017, I'm a little surprised we didn't hit
> this bug until now.
> 
> Has something changed more recently that made it more likely to hit? Or is
> it one of those 'needed people to have more RAM first' or bigger PCI BAR's?

Yeah, frankly, this is the first patch where I could find the splitting being introduced. It might
be more correct to refer to the introduction of 1G huge_pfnmaps?

> 
>> Cc: stable@vger.kernel.org
>> Co-developed-by: David Hildenbrand (Arm) <david@kernel.org>
>> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
>> Signed-off-by: Max Boone <mboone@akamai.com>
> 
> Only nits here, the logic LGTM, so:

I’ll write up a PATCH v2 later today.

> 
> […]



[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3061 bytes --]

  reply	other threads:[~2026-03-18 13:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 14:03 Max Boone via B4 Relay
2026-03-17 14:05 ` David Hildenbrand (Arm)
2026-03-18  6:16 ` Qi Zheng
2026-03-18  7:37   ` Boone, Max
2026-03-18  7:38   ` David Hildenbrand (Arm)
2026-03-18 12:55 ` Lorenzo Stoakes (Oracle)
2026-03-18 13:08   ` Boone, Max [this message]
2026-03-18 13:27     ` Boone, Max
2026-03-18 14:07       ` Lorenzo Stoakes (Oracle)
2026-03-18 14:10     ` Lorenzo Stoakes (Oracle)
2026-03-18 14:30       ` David Hildenbrand (Arm)

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=719CB417-F511-402A-91E3-8A696ABCE0D5@akamai.com \
    --to=mboone@akamai.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@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