From: Hugh Dickins <hughd@google.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-mm@kvack.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Lorenzo Stoakes <ljs@kernel.org>
Subject: Re: [RFC V2 3/3] mm: Replace pgtable entry prints with new format
Date: Fri, 12 Jun 2026 14:26:34 -0700 (PDT) [thread overview]
Message-ID: <4a416383-62f5-1716-8e04-a2ee1f89a864@google.com> (raw)
In-Reply-To: <fc57bb9a-4564-489e-8da4-65068b5283ae@kernel.org>
On Fri, 12 Jun 2026, David Hildenbrand (Arm) wrote:
...
>
> After some off-list discussion, I wonder if we can make our life easier.
>
> I think, even with your patch, there is still the case:
>
> pr_alert("BUG: Bad page map in process %s %s:%08llx", current->comm,
> pgtable_level_to_str(level), entry);
>
> Where we cast all entries to an "unsigned long" in the callers. We'd have to rework all
> that for 128bit entries either way (passing them in some struct instead).
>
> I really just extended what we used to do here in print_bad_pte() before commit ec63a44011d.
>
> Maybe we should just drop the "print the involved page table entries" thing?
>
> I mean, we do have the actual page, and we do have the address in the address space, which
> we all print.
>
> Not sure if the actual page table entries are that relevant?
The page table entry is BUGgily Bad: we want to see what it looks like
(sometimes, a sequence of bad page map entries may even show up as ASCII).
Hugh
next prev parent reply other threads:[~2026-06-12 21:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 4:35 [RFC V2 0/3] lib/vsprintf: Add support for pgtable entries Anshuman Khandual
2026-06-10 4:35 ` [RFC V2 1/3] " Anshuman Khandual
2026-06-10 11:13 ` Usama Arif
2026-06-11 5:15 ` Anshuman Khandual
2026-06-11 7:17 ` Andy Shevchenko
2026-06-11 9:50 ` Anshuman Khandual
2026-06-11 18:59 ` Andy Shevchenko
2026-06-10 4:35 ` [RFC V2 2/3] kunit: printf: Add test " Anshuman Khandual
2026-06-10 4:35 ` [RFC V2 3/3] mm: Replace pgtable entry prints with new format Anshuman Khandual
2026-06-11 11:32 ` David Hildenbrand (Arm)
2026-06-12 11:08 ` David Hildenbrand (Arm)
2026-06-12 21:26 ` Hugh Dickins [this message]
2026-06-15 16:01 ` David Hildenbrand (Arm)
2026-06-16 6:19 ` Hugh Dickins
2026-06-30 13:36 ` David Hildenbrand (Arm)
2026-07-01 9:00 ` Andy Shevchenko
2026-07-02 4:29 ` Anshuman Khandual
2026-07-02 7:32 ` David Hildenbrand (Arm)
2026-07-02 9:04 ` Anshuman Khandual
2026-07-02 9:20 ` Andy Shevchenko
2026-07-02 9:36 ` David Hildenbrand (Arm)
2026-06-11 19:15 ` [RFC V2 0/3] lib/vsprintf: Add support for pgtable entries Matthew Wilcox
2026-06-11 19:33 ` Andy Shevchenko
2026-06-11 19:37 ` Matthew Wilcox
2026-06-12 11:14 ` 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=4a416383-62f5-1716-8e04-a2ee1f89a864@google.com \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@rasmusvillemoes.dk \
--cc=ljs@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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
all inboxes | Powered by JetHome®