From: Catalin Marinas <catalin.marinas@arm.com>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: gregkh@linuxfoundation.org, agordeev@linux.ibm.com,
alexghiti@rivosinc.com, anshuman.khandual@arm.com,
christophe.leroy@csgroup.eu, david@redhat.com, will@kernel.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mm: hugetlb: Add huge page size param to" failed to apply to 6.1-stable tree
Date: Fri, 7 Mar 2025 18:53:20 +0000 [thread overview]
Message-ID: <Z8tAoJpyB8aye2uV@arm.com> (raw)
In-Reply-To: <f1cbc610-e78d-44df-aba1-9c8b392670f2@arm.com>
On Thu, Mar 06, 2025 at 03:52:09PM +0000, Ryan Roberts wrote:
> On 04/03/2025 16:41, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 6.1-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
>
> From v6.1 it becomes non-trivial to backport this patch as it depends on a patch
> that is only present from v6.5; Commit 935d4f0c6dc8 ("mm: hugetlb: add huge page
> size param to set_huge_pte_at()").
>
> Given this is fixing a theoretical bug for which I'm not aware of any actual
> real world triggering, I'm proposing not to backport any further back than v6.6.
> I've already sent the backports for v6.13, v6.12 and v6.6.
It makes sense to me. Thanks Ryan.
--
Catalin
next prev parent reply other threads:[~2025-03-07 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 16:41 FAILED: patch "[PATCH] mm: hugetlb: Add huge page size param to" failed to apply to 6.1-stable tree gregkh
2025-03-06 15:52 ` Ryan Roberts
2025-03-07 18:53 ` Catalin Marinas [this message]
2025-03-10 11:46 ` Greg KH
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=Z8tAoJpyB8aye2uV@arm.com \
--to=catalin.marinas@arm.com \
--cc=agordeev@linux.ibm.com \
--cc=alexghiti@rivosinc.com \
--cc=anshuman.khandual@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=ryan.roberts@arm.com \
--cc=stable@vger.kernel.org \
--cc=will@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.