mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
	 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 11:12:00 +0100	[thread overview]
Message-ID: <ap_XuF3ubLQAJ330@gremlin> (raw)
In-Reply-To: <ap_WIZwCPKB07nAf@kernel.org>

On Tue, Sep 08, 2026 at 12:32:17PM +0300, Mike Rapoport wrote:
> On Tue, Sep 01, 2026 at 04:36:38PM -0700, Dave Hansen wrote:
> > On 9/1/26 00:10, Lorenzo Stoakes (ARM) wrote:
> > > Dave - you've somehow applied this patch completely incorrectly to x86/urgent,
> > > I'm not happy with this going to Linus in this form :/
> >
> > Me neither, btw.
> >
> > So, here it is applied:
> >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/daveh/devel.git/log/?h=cpa1
> >
> > The diffstat exactly matches the mbox that I sucked in. I'm going to
> > launch some tests overnight.
> >
> > The only things I really munged were a little merge issue with patch 1,
> > a SoB ordering issue in patch 3, and a few scattered rewordings in the
> > commit messages.
> >
> > Not pushed to x86/urgent, yet.
>
> I have to say I'm confused with today's batch of tip-bot emails saying Ingo
> applied these to x86/mm :/

Since I don't seem to get replies to mails on this topic, I can only
_guess_ :), but:

* I see patches in x86/urgent that aren't in x86/mm, so that rules out
  x86/mm being a stepping stone in the process.

* x86/urgent has had more patches added to it, for series sent after this
  one, which fix bugs from 2024, 2025 etc. So that's all working as
  expected.

* We've already highlighted that this series fixes bugs users are seeing in
  production, so I don't see why it'd be deprioritised.

* It's coming form a private dev repo/branch so I can't imagine it's a
  wayward script (but maybe?)

* The patches have been in linux-next for a while (maybe Dave/Ingo wanted
  them there longer? They were there for weeks before the ->x86 stuff
  though).

Perhaps the reported bug that you've now fixed was the hold up? I guess who
knows :)

So yeah, I'm also rather confused :)

Ah well.

I guess taking them through the mm tree wouldn't really be sensible/the
right thing to do at this stage, so I guess let's hope they land for 7.4.

>
> --
> Sincerely yours,
> Mike.

--
Cheers, Lorenzo

  reply	other threads:[~2026-09-08 10:12 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) [this message]
2026-09-08 13:58             ` Dave Hansen
2026-09-08 15:14               ` Dave Hansen
2026-09-08 15:17               ` Vlastimil Babka (SUSE)
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=ap_XuF3ubLQAJ330@gremlin \
    --to=ljs@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=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 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®