From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Alexey Panov <apanov@astralinux.ru>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v2 6.1] mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM
Date: Sun, 9 Mar 2025 22:14:51 -0400 [thread overview]
Message-ID: <20250309203432-73c18af6088d5e1a@stable.kernel.org> (raw)
In-Reply-To: <20250307122804.10548-1-apanov@astralinux.ru>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 091c1dd2d4df6edd1beebe0e5863d4034ade9572
WARNING: Author mismatch between patch and upstream commit:
Backport author: Alexey Panov<apanov@astralinux.ru>
Commit author: David Hildenbrand<david@redhat.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 42d9fe2adf86)
6.6.y | Present (different SHA1: a13b2b9b0b0b)
Note: The patch differs from the upstream commit:
---
1: 091c1dd2d4df6 < -: ------------- mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM
-: ------------- > 1: 872437ce0bfb1 mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2025-03-10 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 12:28 [PATCH v2 6.1] mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM Alexey Panov
2025-03-10 2:14 ` Sasha Levin [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=20250309203432-73c18af6088d5e1a@stable.kernel.org \
--to=sashal@kernel.org \
--cc=apanov@astralinux.ru \
--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