From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>, Mike Rapoport <rppt@kernel.org>
Cc: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Jiri Slaby <jirislaby@kernel.org>,
"Kiryl Shutsemau (Meta)" <kas@kernel.org>,
"David Hildenbrand (Arm)" <david@kernel.org>,
Will Deacon <will@kernel.org>, David Carlier <devnexen@gmail.com>,
Atish Patra <atishp@meta.com>, Nikunj A Dadhania <nikunj@amd.com>,
stable@vger.kernel.org, x86@kernel.org,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [tip: x86/urgent] x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF
Date: Tue, 8 Sep 2026 17:17:12 +0200 [thread overview]
Message-ID: <5394f2d7-03e2-4aeb-a5da-60a0368340d9@kernel.org> (raw)
In-Reply-To: <54f55b19-4a42-4c5d-a6ec-979132e11ece@intel.com>
On 9/8/26 15:58, Dave Hansen wrote:
> On 9/8/26 02:32, Mike Rapoport wrote:
>> I have to say I'm confused with today's batch of tip-bot emails saying Ingo
>> applied these to x86/mm :/
>
> Just a reminder that we have x86/urgent which will be going to Linus
> like today. There's also x86/mm which goes up in the next merge window..
However x86/urgent (at least as visible [1]) doesn't contain anything from
this series, and x86/mm has everything except "Fix effective RW computation".
But tip/urgent does merge x86/mm so hopefully it means it's really going to
Linus now-ish (and not next merge window)? It just doesn't have "urgent" in
the branch name?
> The "Fix effective RW computation" patch is getting broken out and is
> going to wait for the next merge window. We don't want it sitting in
> mainline generating warnings, especially false positives like the one
> this weekend. That's not to disparage the patch; it's overall the right
> thing to do.
So that means adding it to x86/mm after the current one is sent as urgent?
Just wanted to double check, thanks.
Vlastimil
[1] https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/
> Sound good?
next prev parent reply other threads:[~2026-09-08 15:17 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 9:01 [PATCH v2 0/5] x86/mm/pat: CPA fixes Mike Rapoport
2026-08-13 9:01 ` [PATCH v2 1/5] x86/mm/pat: acquire init_mm write lock on collapse to avoid UAF Mike Rapoport
2026-08-31 22:27 ` [tip: x86/urgent] x86/mm/pat: Acquire " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-01 6:03 ` Jiri Slaby
2026-09-01 7:10 ` Lorenzo Stoakes (ARM)
2026-09-01 23:36 ` Dave Hansen
2026-09-02 6:53 ` Lorenzo Stoakes (ARM)
2026-09-08 9:32 ` Mike Rapoport
2026-09-08 10:12 ` Lorenzo Stoakes (ARM)
2026-09-08 13:58 ` Dave Hansen
2026-09-08 15:14 ` Dave Hansen
2026-09-08 15:17 ` Vlastimil Babka (SUSE) [this message]
2026-09-08 19:59 ` Dave Hansen
2026-09-08 23:00 ` Update on CPA fixes, x86/urgent and x86/mm Dave Hansen
2026-09-09 6:40 ` Ingo Molnar
2026-09-09 6:45 ` Ingo Molnar
2026-09-02 18:33 ` [tip: x86/urgent] x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-08 7:21 ` [tip: x86/mm] " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-08 22:51 ` [tip: x86/urgent] " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-09 6:44 ` tip-bot2 for Lorenzo Stoakes (ARM)
2026-08-13 9:01 ` [PATCH v2 2/5] x86/mm/pat: acquire init_mm read lock on attribute change " Mike Rapoport
2026-08-31 22:27 ` [tip: x86/urgent] x86/mm/pat: Acquire " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-01 6:05 ` Jiri Slaby
2026-09-01 7:20 ` Lorenzo Stoakes (ARM)
2026-09-01 13:46 ` Dave Hansen
2026-09-02 18:33 ` tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-08 7:21 ` [tip: x86/mm] x86/mm/pat: Acquire init_mm read lock on attribute changes " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-08 22:51 ` [tip: x86/urgent] " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-09 6:44 ` tip-bot2 for Lorenzo Stoakes (ARM)
2026-08-13 9:01 ` [PATCH v2 3/5] x86/alternative: exclude text poking against change_page_attr() Mike Rapoport
2026-08-25 9:37 ` Jiri Slaby
2026-08-31 22:27 ` [tip: x86/urgent] x86/alternative: Exclude " tip-bot2 for Pedro Falcato
2026-09-01 6:16 ` Jiri Slaby
2026-09-01 7:18 ` Lorenzo Stoakes (ARM)
2026-09-01 7:22 ` Jiri Slaby
2026-09-01 7:24 ` Lorenzo Stoakes (ARM)
2026-09-02 18:33 ` tip-bot2 for Pedro Falcato
2026-09-08 7:21 ` [tip: x86/mm] x86/alternatives: " tip-bot2 for Pedro Falcato
2026-09-08 22:51 ` [tip: x86/urgent] " tip-bot2 for Pedro Falcato
2026-09-09 6:44 ` tip-bot2 for Pedro Falcato
2026-08-13 9:01 ` [PATCH v2 4/5] x86/mm/pat: allocate split page tables as kernel page tables Mike Rapoport
2026-08-31 22:27 ` [tip: x86/urgent] x86/mm/pat: Allocate " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-02 18:33 ` tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-08 7:21 ` [tip: x86/mm] " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-08 22:51 ` [tip: x86/urgent] " tip-bot2 for Lorenzo Stoakes (ARM)
2026-09-09 6:44 ` tip-bot2 for Lorenzo Stoakes (ARM)
2026-08-13 9:01 ` [PATCH v2 5/5] x86/mm/pat: fix effective RW computation in lookup_address_in_pgd_attr() Mike Rapoport (Microsoft)
2026-08-13 9:45 ` Lorenzo Stoakes (ARM)
2026-08-31 22:27 ` [tip: x86/urgent] x86/mm/pat: Fix " tip-bot2 for Mike Rapoport (Microsoft)
2026-09-02 18:33 ` tip-bot2 for Mike Rapoport (Microsoft)
2026-09-05 4:42 ` Nathan Chancellor
2026-09-06 14:50 ` Dave Hansen
2026-09-06 18:12 ` Nathan Chancellor
2026-09-06 19:12 ` Dave Hansen
2026-09-06 19:52 ` Mike Rapoport
2026-09-07 6:46 ` Mike Rapoport
2026-09-07 22:28 ` Nathan Chancellor
2026-09-08 9:29 ` Mike Rapoport
2026-09-08 22:52 ` [tip: x86/mm] " tip-bot2 for Mike Rapoport (Microsoft)
2026-08-13 15:05 ` [PATCH v2 0/5] x86/mm/pat: CPA fixes Nikunj A. Dadhania
2026-08-13 15:07 ` Lorenzo Stoakes (ARM)
2026-08-13 15:23 ` Pedro Falcato
2026-08-13 17:13 ` Andrew Morton
2026-08-25 7:12 ` Atish Patra
2026-08-25 7:31 ` Lorenzo Stoakes (ARM)
2026-08-25 20:05 ` Atish Patra
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=5394f2d7-03e2-4aeb-a5da-60a0368340d9@kernel.org \
--to=vbabka@kernel.org \
--cc=atishp@meta.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=devnexen@gmail.com \
--cc=jirislaby@kernel.org \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mingo@kernel.org \
--cc=nikunj@amd.com \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=will@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 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.