From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Peter Xu <peterx@redhat.com>
Cc: Pavel Tatashin <pasha.tatashin@soleen.com>,
axelrasmussen@google.com, David Hildenbrand <david@redhat.com>,
nadav.amit@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: 6.10/bisected/regression - commit 8430557fc584 cause warning at mm/page_table_check.c:198 __page_table_check_ptes_set+0x306
Date: Wed, 22 May 2024 03:21:04 +0500 [thread overview]
Message-ID: <CABXGCsOZnxrSHd0y6QrFhzAiY-uTJiRSmo__C_P8Y2qjFV6bRA@mail.gmail.com> (raw)
In-Reply-To: <Zk0UA6wABOB9X_Dx@x1n>
On Wed, May 22, 2024 at 2:37 AM Peter Xu <peterx@redhat.com> wrote:
> Hmm I still cannot reproduce. Weird.
>
> Would it be possible for you to identify which line in debug_vm_pgtable.c
> triggered that issue?
>
> I think it should be some set_pte_at() but I'm not sure, as there aren't a
> lot and all of them look benign so far. It could be that I missed
> something important.
I hope it's helps:
> sh /usr/src/kernels/(uname -r)/scripts/faddr2line /lib/debug/lib/modules/(uname -r)/vmlinux debug_vm_pgtable+0x1c04
debug_vm_pgtable+0x1c04/0x3360:
native_ptep_get_and_clear at arch/x86/include/asm/pgtable_64.h:94
(inlined by) ptep_get_and_clear at arch/x86/include/asm/pgtable.h:1262
(inlined by) ptep_clear at include/linux/pgtable.h:509
(inlined by) pte_clear_tests at mm/debug_vm_pgtable.c:643
(inlined by) debug_vm_pgtable at mm/debug_vm_pgtable.c:1392
> cat -n /usr/src/debug/kernel-6.9-10323-g8f6a15f095a6/linux-6.10.0-0.rc0.20240521git8f6a15f095a6.10.fc41.x86_64/mm/debug_vm_pgtable.c | sed -n '1387,1397 p'
1387 * Page table modifying tests. They need to hold
1388 * proper page table lock.
1389 */
1390
1391 args.ptep = pte_offset_map_lock(args.mm, args.pmdp, args.vaddr, &ptl);
1392 pte_clear_tests(&args);
1393 pte_advanced_tests(&args);
1394 if (args.ptep)
1395 pte_unmap_unlock(args.ptep, ptl);
1396
1397 ptl = pmd_lock(args.mm, args.pmdp);
--
Best Regards,
Mike Gavrilov.
next prev parent reply other threads:[~2024-05-21 22:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 20:17 Mikhail Gavrilov
2024-05-21 20:44 ` Peter Xu
2024-05-21 20:48 ` Mikhail Gavrilov
2024-05-21 21:37 ` Peter Xu
2024-05-21 22:21 ` Mikhail Gavrilov [this message]
[not found] ` <Zk0h0V8kvZRKu6F4@x1n>
2024-05-21 23:26 ` Mikhail Gavrilov
2024-05-22 7:48 ` David Hildenbrand
2024-05-22 15:18 ` Peter Xu
2024-05-22 15:34 ` David Hildenbrand
2024-05-22 16:10 ` Peter Xu
2024-05-22 16:13 ` Peter Xu
2024-05-22 20:25 ` David Hildenbrand
2024-05-23 6:34 ` Mikhail Gavrilov
2024-05-23 13:19 ` Peter Xu
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=CABXGCsOZnxrSHd0y6QrFhzAiY-uTJiRSmo__C_P8Y2qjFV6bRA@mail.gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nadav.amit@gmail.com \
--cc=pasha.tatashin@soleen.com \
--cc=peterx@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox