From: Dave Hansen <dave.hansen@intel.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Lu Baolu <baolu.lu@linux.intel.com>,
Lance Yang <lance.yang@linux.dev>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] x86/mm: fix freeing of PMD-sized vmemmap pages
Date: Wed, 27 May 2026 11:31:32 -0700 [thread overview]
Message-ID: <bedd3f11-9077-4ddc-89dc-e21ee7aaab48@intel.com> (raw)
In-Reply-To: <db4b46c4-823d-4756-a439-058199a9116e@kernel.org>
On 5/22/26 15:35, David Hildenbrand (Arm) wrote:
>> I'm not seeing this in linux-next so I (re) queued it in mm.git's
>> mm-hotfixes-unstble queue, for a 7.1-rcX merge.
> Thanks. Dave is aware and didn't get to it yet.
>
> So I'll let him speak up if he wants to let this sit a bit longer here.
This isn't a new bug and it's getting a bit late in the -rc's. I'll
queue it for the next merge window.
Thanks for the reminder.
next prev parent reply other threads:[~2026-05-27 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 10:49 David Hildenbrand (Arm)
2026-04-29 15:29 ` Lance Yang
2026-05-08 9:19 ` David Hildenbrand (Arm)
2026-05-08 9:23 ` Peter Zijlstra
2026-05-08 10:51 ` David Hildenbrand (Arm)
2026-05-22 0:35 ` Andrew Morton
2026-05-22 22:35 ` David Hildenbrand (Arm)
2026-05-27 18:31 ` Dave Hansen [this message]
2026-05-27 18:43 ` [tip: x86/mm] x86/mm: Fix " tip-bot2 for David Hildenbrand (Arm)
2026-05-27 22:51 ` [PATCH v2] x86/mm: fix " Alison Schofield
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=bedd3f11-9077-4ddc-89dc-e21ee7aaab48@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolu.lu@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=hpa@zytor.com \
--cc=jgg@ziepe.ca \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--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
Powered by JetHome