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 22:15:15 +0100 [thread overview]
Message-ID: <44967e53-d514-4323-b41d-8f672db0f97e@kernel.org> (raw)
In-Reply-To: <CANfXJztnmhn8AU66EjQ+G=vx_0VQKu8w8O-wYrTjHxBD_OaaFA@mail.gmail.com>
On 3/9/26 21:42, Tytus Rogalewski wrote:
> Hi,
>
> Well it seemed "like mem leak" but honestly it was my bad assumption i
> guess.
>
> And does it correlate with io_uring somehow ?
Not really :/
> Because i have no such issues when using threads mode in proxmox with
> network drive that is on fuse.
> Could be that triggered perhaps when someone was writing hard to his
> disk and that would cause other fuse drives to hung for few secs and
> that would trigger that BUG ?
I'm rather wondering whether something involving io_uring could make the
kernel reschedule more often, possibly in the race window that the issue
I linked describes.
> And using threads somehow fixes that issue ? Does that make any sense ?
Maybe with io_uring there could be more threads, the question is how
many io-threads QEMU would be using in your setup. Hard to tell.
--
Cheers,
David
prev parent reply other threads:[~2026-03-09 21:15 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)
2026-03-09 20:42 ` Tytus Rogalewski
2026-03-09 21:15 ` 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=44967e53-d514-4323-b41d-8f672db0f97e@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.