From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>,
"Boone, Max" <mboone@akamai.com>
Cc: Andrew Morton <akpm@linux-foundation.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 15:30:36 +0100 [thread overview]
Message-ID: <70848e13-b272-4a46-84b7-d5f217f82be9@kernel.org> (raw)
In-Reply-To: <789b4585-7542-412a-b9ab-3f7de8d8dc89@lucifer.local>
>>>
>>> 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?
>
> Yeah maybe that makes more sense? David - what do you think?
I'm not sure whether DAX with PUDs could trigger something similar?
--
Cheers,
David
prev parent reply other threads:[~2026-03-18 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 14:03 [PATCH] mm/pagewalk: fix race between concurrent split and refault 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
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) [this message]
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=70848e13-b272-4a46-84b7-d5f217f82be9@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mboone@akamai.com \
--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