mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
	 Andrew Morton <akpm@linux-foundation.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	 "Liam R . Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	 Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	 Michal Hocko <mhocko@suse.com>,
	Vishal Moola <vishal.moola@gmail.com>,
	 Ingo Molnar <mingo@kernel.org>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	 Jason Gunthorpe <jgg@nvidia.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	x86@kernel.org,  linux-mm@kvack.org, regressions@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: don't defer freeing kernel page tables while booting
Date: Thu, 24 Sep 2026 09:57:57 +0100	[thread overview]
Message-ID: <arTl5Cc1B-2_BoHP@gremlin> (raw)
In-Reply-To: <65b94694-d503-46c5-9f13-f0f7f8bba8d8@kernel.org>

On Thu, Sep 24, 2026 at 09:31:40AM +0200, David Hildenbrand (Arm) wrote:
> On 9/24/26 09:28, Mikhail Gavrilov wrote:
> > On 9/24/26 09:07, David Hildenbrand (Arm) wrote:
> >> Should we instead simply skip the
> >>
> >> 	schedule_work(&kernel_pgtable_work.work);
> >>
> >> and rely on anybody freeing stuff later to just free that one alongside?
> >>
> >> That avoids throwing in more freeing handling.
> >
> > Yes, that is simpler, and the early table then goes through the same
> > IOMMU flush as every other one, so there is no need to reason about
> > what an IOMMU can see during boot.  The only cost is that it waits on
> > the list until the next kernel page table is freed after boot.
>
> If we're worried about that actually causing problems we could drain the list at
> a later part during the boot stage. I'd suspect we free something else later
> already and simply drain the list ...

Yup agreed this is the best fix.

Please go ahead with that Mikhail.

I hate that the Fixes: is a patch that actually makes the CPA code do the right
thing rather than the fact this whole code path is possible this early, but it
is the correct one from the point of view of what exposes the bug.

>
> --
> Cheers,
>
> David

--
Cheers, Lorenzo

  reply	other threads:[~2026-09-24  8:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24  6:43 Mikhail Gavrilov
2026-09-24  7:07 ` David Hildenbrand (Arm)
2026-09-24  7:28   ` Mikhail Gavrilov
2026-09-24  7:31     ` David Hildenbrand (Arm)
2026-09-24  8:57       ` Lorenzo Stoakes (ARM) [this message]
2026-09-24  8:59         ` Lorenzo Stoakes (ARM)
2026-09-24  9:29           ` Lorenzo Stoakes (ARM)
2026-09-24  7:38     ` Lorenzo Stoakes (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=arTl5Cc1B-2_BoHP@gremlin \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=david@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=mikhail.v.gavrilov@gmail.com \
    --cc=mingo@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=vishal.moola@gmail.com \
    --cc=x86@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®