mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Guilherme Giacomo Simoes <trintaeoitogc@gmail.com>,
	akpm@linux-foundation.org, ljs@kernel.org, liam@infradead.org,
	vbabka@kernel.org, rppt@kernel.org, surenb@google.com,
	mhocko@suse.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: clear pmd in pmdp_invalidate()
Date: Tue, 27 Oct 2026 13:11:24 +0100	[thread overview]
Message-ID: <f1b2ec5a-f7a7-442c-97fd-f67fe6ecb197@kernel.org> (raw)
In-Reply-To: <20261027113813.1332096-1-trintaeoitogc@gmail.com>

On 10/27/26 12:38, Guilherme Giacomo Simoes wrote:
> when attempt to do a madvise in a chunk of memory allocated by mmap, the
> folio_split is called to split a portion of memory, and despite the path
> leads to pmd_mkinvalid() they do not clear the pmd and clearer wording,
> leading to a BUG_ON inside page_table_check_set() because the map count
> is more than 1.
> 
> Call the page_table_check_pmd_clear() inside pmdp_invalidate() generic
> function to ensure that the pmd will have they map count decrement.
> 

The subject + description is rather confusing: you are not "clearing the pmd",
you tell page-table-check that the PMD was cleared.

This is all about apge-table-check.

Can you post the actual kernel splat you ran into? Or is this generated by an LLM?

Thanks!

-- 
Cheers,

David

  reply	other threads:[~2026-10-27 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 11:38 Guilherme Giacomo Simoes
2026-10-27 12:11 ` David Hildenbrand (Arm) [this message]
2026-10-27 14:09   ` Guilherme Giacomo Simoes
2026-10-27 14:50     ` Guilherme Giacomo Simoes
2026-10-27 23:10 ` [syzbot ci] " syzbot ci

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=f1b2ec5a-f7a7-442c-97fd-f67fe6ecb197@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=trintaeoitogc@gmail.com \
    --cc=vbabka@kernel.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®