From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, kirill.shutemov@linux.intel.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] mm: fix apply_to_existing_page_range()
Date: Tue, 22 Apr 2025 15:17:37 -0400 [thread overview]
Message-ID: <20250422125653-4ac90e6cf3112bb5@stable.kernel.org> (raw)
In-Reply-To: <20250422053722.881707-1-kirill.shutemov@linux.intel.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: a995199384347261bb3f21b2e171fa7f988bd2f8
Status in newer kernel trees:
6.14.y | Not found
6.12.y | Not found
6.6.y | Not found
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: a995199384347 ! 1: 35ec614cdbbfe mm: fix apply_to_existing_page_range()
@@ Commit message
Cc: Vlastimil Babka <vbabka@suse.cz>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
+ (cherry picked from commit a995199384347261bb3f21b2e171fa7f988bd2f8)
+ Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
## mm/memory.c ##
@@ mm/memory.c: static int apply_to_pte_range(struct mm_struct *mm, pmd_t *pmd,
if (fn) {
do {
- if (create || !pte_none(ptep_get(pte))) {
+ if (create || !pte_none(*pte)) {
- err = fn(pte++, addr, data);
+ err = fn(pte, addr, data);
if (err)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
prev parent reply other threads:[~2025-04-22 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 13:57 FAILED: patch "[PATCH] mm: fix apply_to_existing_page_range()" failed to apply to 5.15-stable tree gregkh
2025-04-22 5:37 ` [PATCH 5.15.y] mm: fix apply_to_existing_page_range() Kirill A. Shutemov
2025-04-22 19:17 ` 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=20250422125653-4ac90e6cf3112bb5@stable.kernel.org \
--to=sashal@kernel.org \
--cc=kirill.shutemov@linux.intel.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