From: Andrew Morton <akpm@linux-foundation.org>
To: Gregory Price <gourry@gourry.net>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
liam@infradead.org, ljs@kernel.org, vbabka@kernel.org,
jannh@google.com, pfalcato@suse.de, peterx@redhat.com,
jgg@ziepe.ca, david@kernel.org,
sashiko-bot <sashiko-bot@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] proc/task_mmu: handle special PMDs in clear_refs and pagemap
Date: Mon, 14 Sep 2026 23:11:18 -0700 [thread overview]
Message-ID: <20260914231118.ac170fb8c2c105412adfedd3@linux-foundation.org> (raw)
In-Reply-To: <aqjS0xWes7fhhI9A@gourry-fedora-PF4VCD3F>
On Tue, 15 Sep 2026 01:19:50 -0400 Gregory Price <gourry@gourry.net> wrote:
> > > Fixes: 3c8e44c9b369 ("mm: mark special bits for huge pfn mappings when inject")
> > > Cc: <stable@vger.kernel.org> # v6.19+
> >
> > Why cc:stable? Is a crafted test driver the only way of hitting this?
> >
>
> Technically reachable via mshv_vtl_low, so i tagged it stable.
I have no idea what this means, but I pasted it in ;)
> It's hard to make a judgment call on some of these - so I err on the
> side of backporting. Feel free to drop stable if you think it's not
> worth it.
I retained the cc:stable. It's disturbing to leave known bugs in there
because we *think* nobody can reach them. What if we're wrong about that?
prev parent reply other threads:[~2026-09-15 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 12:28 Gregory Price
2026-09-15 4:49 ` Andrew Morton
2026-09-15 5:19 ` Gregory Price
2026-09-15 6:11 ` Andrew Morton [this message]
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=20260914231118.ac170fb8c2c105412adfedd3@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=kernel-team@meta.com \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=peterx@redhat.com \
--cc=pfalcato@suse.de \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vbabka@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®