From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Tytus Rogalewski <tytanick@gmail.com>
Cc: linux-mm@kvack.org, muchun.song@linux.dev, osalvador@suse.de,
Jens Axboe <axboe@kernel.dk>
Subject: Re: walk_pgd_range BUG: unable to handle page fault
Date: Mon, 9 Mar 2026 21:27:32 +0100 [thread overview]
Message-ID: <ca6248a2-c442-4fe1-bf4d-9b9f6ba2de85@kernel.org> (raw)
In-Reply-To: <5f4d8780-55f1-4b60-840a-056da7401848@kernel.org>
On 3/5/26 12:40, David Hildenbrand (Arm) wrote:
> On 3/5/26 12:39, Tytus Rogalewski wrote:
>> I had this problem on 6.19-rc4 yes. I saw it. But i cant reproduce it
>> NOW - this is what i ment :)
>
> Ah, thanks for clarifying, makes sense!
>
The following issue might explain the problem:
https://lore.kernel.org/r/20260309174949.2514565-1-mboone@akamai.com
It would be related to what I recently said: "vfio recently gained
support for installing huge mappings into user page tables."
smaps_walk_ops() does not have a pud_entry() callback, so we'd try to
split (unmap). If that happens concurrently with a refault, we might be
able to trigger a BUG.
But it wouldn't explain any memory leak.
--
Cheers,
David
next prev parent reply other threads:[~2026-03-09 20:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANfXJzt4P+FCkdL_=FfmG80_bY8FkzSocJSPeksSQ_vXObRNOQ@mail.gmail.com>
2026-02-04 21:52 ` walk_pgd_range BUG: unable to handle page fault David Hildenbrand (arm)
2026-02-04 22:24 ` Tytus Rogalewski
2026-02-04 22:50 ` Tytus Rogalewski
2026-02-05 12:44 ` David Hildenbrand (Arm)
2026-02-05 12:46 ` Tytus Rogalewski
2026-02-05 12:57 ` David Hildenbrand (Arm)
2026-02-05 13:20 ` Tytus Rogalewski
2026-03-05 8:11 ` Tytus Rogalewski
2026-03-05 11:17 ` David Hildenbrand (Arm)
2026-03-05 11:29 ` Tytus Rogalewski
2026-03-05 11:33 ` David Hildenbrand (Arm)
2026-03-05 11:34 ` Tytus Rogalewski
2026-03-05 11:38 ` David Hildenbrand (Arm)
2026-03-05 11:39 ` Tytus Rogalewski
2026-03-05 11:40 ` David Hildenbrand (Arm)
2026-03-09 20:27 ` David Hildenbrand (Arm) [this message]
2026-03-09 20:42 ` Tytus Rogalewski
2026-03-09 21:15 ` 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=ca6248a2-c442-4fe1-bf4d-9b9f6ba2de85@kernel.org \
--to=david@kernel.org \
--cc=axboe@kernel.dk \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=tytanick@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.