linux-kernel - [bug/bisected] I see "mm/pgtable-generic.c:53: bad pmd (____ptrval___

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABXGCsN3JqXckWO=V7p=FhPU1tK03RE1w9UE6xL5Y86SMk209w@mail.gmail.com>
Date:   Sat, 15 Jul 2023 14:24:59 +0500
From:   Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To:     Linux Memory Management List <linux-mm@...ck.org>,
        Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        hughd@...gle.com
Subject: [bug/bisected] I see "mm/pgtable-generic.c:53: bad pmd
 (____ptrval____)(8000000100077061)" every boot time

Hi,
It's ok that I see "mm/pgtable-generic.c:53: bad pmd
(____ptrval____)(8000000100077061)" every boot time?
Unfortunately bisect couldn't say which of commits
# possible first bad commit:
[be872f83bf571f4f9a0ac25e2c9c36e905a36619] mm/pagewalk:
walk_pte_range() allow for pte_offset_map()
# possible first bad commit:
[7780d04046a2288ab85d88bedacc60fa4fad9971] mm/pagewalkers:
ACTION_AGAIN if pte_offset_map_lock() fails
# possible first bad commit:
[2798bbe75b9c2752b46d292e5c2a49f49da36418] mm/page_vma_mapped:
pte_offset_map_nolock() not pte_lockptr()
# possible first bad commit:
[90f43b0a13cddb09e2686f4d976751c0a9b8b197] mm/page_vma_mapped:
reformat map_pte() with less indentation
# possible first bad commit:
[45fe85e9811ede2d65b21724cae50d6a0563e452] mm/page_vma_mapped: delete
bogosity in page_vma_mapped_walk()
# possible first bad commit:
[65747aaf42b7db6acb8e57a2b8e9959928f404dd] mm/filemap: allow
pte_offset_map_lock() to fail
# possible first bad commit:
[0d940a9b270b9220dcff74d8e9123c9788365751] mm/pgtable: allow
pte_offset_map[_lock]() to fail
definitely first bad because my machine on which I am was doing
bisection is unbootable on these commits.
I hope Hugh Dickins can figure out what's going on here. He is the
author of these commits.

All mine machines are based on the AMD platform two 7950X and one 5900HX.

It seems that this message is harmless for the system in any way, but
I can't judge it is a bug or not.
>From the user side it looks like regression because on commit
46c475bd676bb05077c8a38b37f175552f035406 this message was absent.

-- 
Best Regards,
Mike Gavrilov.

View attachment "bisect-log-bad-pmd.txt" of type "text/plain" (3840 bytes)

Download attachment "dmesg.zip" of type "application/zip" (62748 bytes)