From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, catalin.marinas@arm.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH stable 5.10.y-6.12.y] arm64: mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
Date: Thu, 20 Feb 2025 12:52:59 -0500 [thread overview]
Message-ID: <20250220123630-be1fcd2241843e8a@stable.kernel.org> (raw)
In-Reply-To: <20250220155801.1731061-1-catalin.marinas@arm.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Could not find matching upstream commit
No upstream commit was identified. Using temporary commit for testing.
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
| stable/linux-5.10.y | Success | Success |
next prev parent reply other threads:[~2025-02-20 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 15:58 [PATCH stable 5.10.y-6.12.y] arm64: mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings Catalin Marinas
2025-02-20 16:39 ` Greg Kroah-Hartman
2025-02-20 17:52 ` Sasha Levin [this message]
2025-02-21 15:17 ` Greg Kroah-Hartman
2025-02-21 15:36 ` Catalin Marinas
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=20250220123630-be1fcd2241843e8a@stable.kernel.org \
--to=sashal@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=stable@vger.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