From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, myrrhperiwinkle@qtmlabs.xyz
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4.y 5.10.y 5.15.y 6.1.y 6.6.y 6.12.y 6.13.y 6.14.y] x86/e820: Fix handling of subpage regions when calculating nosave ranges in e820__register_nosave_regions()
Date: Fri, 18 Apr 2025 11:42:36 -0400 [thread overview]
Message-ID: <20250418093106-0299edfc32afe6d7@stable.kernel.org> (raw)
In-Reply-To: <20250417123848.81215-2-myrrhperiwinkle@qtmlabs.xyz>
[ 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: f2f29da9f0d4367f6ff35e0d9d021257bb53e273
Status in newer kernel trees:
6.14.y | Not found
6.13.y | Not found
6.12.y | Not found
6.6.y | Not found
6.1.y | Not found
5.15.y | Not found
5.10.y | Not found
Note: The patch differs from the upstream commit:
---
1: f2f29da9f0d43 ! 1: f3ea523486c43 x86/e820: Fix handling of subpage regions when calculating nosave ranges in e820__register_nosave_regions()
@@ Commit message
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/20250406-fix-e820-nosave-v3-1-f3787bc1ee1d@qtmlabs.xyz
Closes: https://lore.kernel.org/all/Z4WFjBVHpndct7br@desktop0a/
+ (cherry picked from commit f2f29da9f0d4367f6ff35e0d9d021257bb53e273)
+ Signed-off-by: Myrrh Periwinkle <myrrhperiwinkle@qtmlabs.xyz>
## arch/x86/kernel/e820.c ##
@@ arch/x86/kernel/e820.c: void __init e820__memory_setup_extended(u64 phys_addr, u32 data_len)
@@ arch/x86/kernel/e820.c: void __init e820__memory_setup_extended(u64 phys_addr, u
-
- pfn = PFN_DOWN(entry->addr + entry->size);
-
- if (entry->type != E820_TYPE_RAM)
+ if (entry->type != E820_TYPE_RAM && entry->type != E820_TYPE_RESERVED_KERN)
- register_nosave_region(PFN_UP(entry->addr), pfn);
+ continue;
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y | Success | Success |
| stable/linux-5.10.y | Success | Success |
| stable/linux-5.15.y | Success | Success |
| stable/linux-6.1.y | Success | Success |
| stable/linux-6.6.y | Success | Success |
| stable/linux-6.12.y | Success | Success |
| stable/linux-6.13.y | Success | Success |
| stable/linux-6.14.y | Success | Success |
prev parent reply other threads:[~2025-04-18 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 12:24 FAILED: patch "[PATCH] x86/e820: Fix handling of subpage regions when calculating" failed to apply to 5.4-stable tree gregkh
2025-04-17 12:38 ` [PATCH 5.4.y 5.10.y 5.15.y 6.1.y 6.6.y 6.12.y 6.13.y 6.14.y] x86/e820: Fix handling of subpage regions when calculating nosave ranges in e820__register_nosave_regions() Myrrh Periwinkle
2025-04-18 15:42 ` 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=20250418093106-0299edfc32afe6d7@stable.kernel.org \
--to=sashal@kernel.org \
--cc=myrrhperiwinkle@qtmlabs.xyz \
--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 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.