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:27:33 +0000 [thread overview]
Message-ID: <E9058409-F4D6-4146-9366-17E87FAC9812@akamai.com> (raw)
In-Reply-To: <719CB417-F511-402A-91E3-8A696ABCE0D5@akamai.com>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
> On Mar 18, 2026, at 2:08 PM, Max Boone <mboone@akamai.com> wrote:
>>
>> 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?
Forgot to mention, but yeah, we’re seeing this on Blackwell cards which have very
large BARs, so probably seeing it first because of that. But the window was already
pretty small, it’s not a very logical thing to poll numa_maps or smaps walks while the
firmware of a VM is remapping the BARs of a GPU. With regards to that specific case
there’s a proxmox thread and mail from the same person presumably [1, 2] that mentions
the same bug.
[1] https://forum.proxmox.com/threads/walk_pgd_range-crash-pve9-1-on-6-18.179895/
[2] https://lore.kernel.org/all/5948f3a6-8f30-4c45-9b86-2af9a6b37405@kernel.org/
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3061 bytes --]
next prev parent reply other threads:[~2026-03-18 13:28 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
2026-03-18 13:27 ` Boone, Max [this message]
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=E9058409-F4D6-4146-9366-17E87FAC9812@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