All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.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: Tue, 21 May 2024 17:37:07 -0400	[thread overview]
Message-ID: <Zk0UA6wABOB9X_Dx@x1n> (raw)
In-Reply-To: <CABXGCsNbcMn0Z0RudFrBW78rZPE+cDY+f9r+yKf_AZwJZUOrQg@mail.gmail.com>

On Wed, May 22, 2024 at 01:48:36AM +0500, Mikhail Gavrilov wrote:
> On Wed, May 22, 2024 at 1:45 AM Peter Xu <peterx@redhat.com> wrote:
> >
> >
> > Did you forget to attach the kernel config?  If so, please attach it, I'll
> > try that, as my local config won't reproduce with CONFIG_DEBUG_VM_PGTABLE=y.
> >
> 
> Oh, sorry.
> Now I've definitely attached it.

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.

Thanks,

-- 
Peter Xu



  reply	other threads:[~2024-05-21 21:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 20:17 6.10/bisected/regression - commit 8430557fc584 cause warning at mm/page_table_check.c:198 __page_table_check_ptes_set+0x306 Mikhail Gavrilov
2024-05-21 20:44 ` Peter Xu
2024-05-21 20:48   ` Mikhail Gavrilov
2024-05-21 21:37     ` Peter Xu [this message]
2024-05-21 22:21       ` Mikhail Gavrilov
2024-05-21 22:36         ` Peter Xu
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=Zk0UA6wABOB9X_Dx@x1n \
    --to=peterx@redhat.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=mikhail.v.gavrilov@gmail.com \
    --cc=nadav.amit@gmail.com \
    --cc=pasha.tatashin@soleen.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.