From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "David Hildenbrand (Red Hat)" <david@kernel.org>,
David Wang <00107082@163.com>,
lance.yang@linux.dev, b-padhi@ti.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, Jan Polensky <japo@linux.ibm.com>
Subject: Re: Linux 6.18-rc6
Date: Wed, 19 Nov 2025 15:42:28 +0000 [thread overview]
Message-ID: <aR3lZHAJJKZg8LRG@arm.com> (raw)
In-Reply-To: <CAHk-=wgT47fDJhjVkiwaVmKCQKkVqRZTaw3LKsaoX-y-df7uhg@mail.gmail.com>
On Tue, Nov 18, 2025 at 08:49:42AM -0800, Linus Torvalds wrote:
> On Mon, 17 Nov 2025 at 23:28, David Hildenbrand (Red Hat)
> <david@kernel.org> wrote:
> >
> > Do you want to quickly send that patch with linux-mm on CC or do you
> > just want to commit it? If you're busy I can quickly send it around.
>
> I applied it (with your fix for the silly inverted assignment to
> 'init') directly, since I wanted to get this fixed quickly as we're
> fairly late in the release cycle.
>
> But if there is some thread on linux-mm that should be notified that
> you know of - this is the only one I'm personally aware of - please do
> give people there a heads-up.
Thanks Linus, David for the quick fix and upstreaming. I tested it as
well on arm64 and works fine both with MTE enabled and disabled. I had a
somewhat similar proposal here:
https://lore.kernel.org/r/aRIEkLw7BofLjOWs@arm.com
though dealing with all pages in tag_clear_highpages() is better, it
gives us some room for (small) optimisation later on (e.g. only flag the
head of a compound page like we do for hugetlb).
--
Catalin
next prev parent reply other threads:[~2025-11-19 15:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-16 22:42 Linux 6.18-rc6 Linus Torvalds
2025-11-17 8:20 ` David Wang
2025-11-17 10:33 ` Linus Torvalds
2025-11-17 12:56 ` David Wang
2025-11-17 13:30 ` David Hildenbrand (Red Hat)
2025-11-17 13:45 ` David Wang
2025-11-17 14:08 ` David Hildenbrand (Red Hat)
2025-11-17 15:28 ` David Wang
2025-11-17 16:59 ` Xi Ruoyao
2025-11-17 21:19 ` Joan Bruguera Micó
2025-11-17 17:28 ` Linus Torvalds
2025-11-17 17:53 ` David Hildenbrand (Red Hat)
2025-11-17 17:59 ` Linus Torvalds
2025-11-17 18:24 ` David Hildenbrand (Red Hat)
2025-11-17 19:17 ` David Hildenbrand (Red Hat)
2025-11-18 1:10 ` Linus Torvalds
2025-11-18 4:13 ` David Wang
2025-11-18 13:55 ` David Wang
2025-11-18 14:12 ` David Hildenbrand (Red Hat)
2025-11-18 14:33 ` David Wang
2025-11-18 14:44 ` Carlos Llamas
2025-11-18 14:51 ` David Hildenbrand (Red Hat)
2025-11-18 14:53 ` Carlos Llamas
2025-11-18 15:09 ` David Wang
2025-11-18 7:28 ` David Hildenbrand (Red Hat)
2025-11-18 16:49 ` Linus Torvalds
2025-11-19 15:42 ` Catalin Marinas [this message]
2025-11-18 3:59 ` Carlos Llamas
2025-11-17 16:42 ` Linus Torvalds
2025-11-17 18:13 ` Guenter Roeck
2025-11-18 17:23 ` Stephanie Gawroriski
2025-11-18 18:01 ` Linus Torvalds
2025-11-18 20:18 ` Stephanie Gawroriski
2025-11-19 9:08 ` Heikki Krogerus
2025-11-19 14:18 ` Stephanie Gawroriski
2025-11-19 15:04 ` Stephanie Gawroriski
2025-11-24 9:50 ` Heikki Krogerus
2025-11-26 16:01 ` Stephanie Gawroriski
2025-11-27 9:53 ` Heikki Krogerus
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=aR3lZHAJJKZg8LRG@arm.com \
--to=catalin.marinas@arm.com \
--cc=00107082@163.com \
--cc=akpm@linux-foundation.org \
--cc=b-padhi@ti.com \
--cc=david@kernel.org \
--cc=japo@linux.ibm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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