From: Dave Hansen <dave.hansen@linux.intel.com>
To: torvalds@linux-foundation.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: [GIT PULL] x86/kdump for 7.4-rc1
Date: Mon, 19 Oct 2026 08:07:04 -0700 [thread overview]
Message-ID: <20261019150704.1851215-1-dave.hansen@linux.intel.com> (raw)
Hi Linus,
Please pull some x86/kdump changes for 7.4-rc1. Some kdump code is
using NR_CPUS_DEFAULT as if it were the actual, in-use max number of
CPUs. Move it over to use NR_CPUS instead.
I suspect this one being in-tree for a few years means that the vast
majority of kdump users are on distro kernels that don't drop NR_CPUS
below the defaults.
--
The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_kdump_for_7.4-rc1
for you to fetch changes up to d949fa7b1ec54c626b656f873b95d76b8ab0d143:
crash: Update stale NR_CPUS_DEFAULT references in elfcorehdr sizing docs (2026-09-02 14:25:16 -0700)
----------------------------------------------------------------
- Resolve NR_CPUS versus NR_CPUS_DEFAULT confusion
----------------------------------------------------------------
Ionut Nechita (2):
x86/crash: Reserve elfcorehdr for CONFIG_NR_CPUS, not CONFIG_NR_CPUS_DEFAULT
crash: Update stale NR_CPUS_DEFAULT references in elfcorehdr sizing docs
arch/x86/kernel/crash.c | 6 +++---
kernel/Kconfig.kexec | 2 +-
kernel/crash_core.c | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
next reply other threads:[~2026-10-19 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 15:07 Dave Hansen [this message]
2026-10-20 22:37 ` pr-tracker-bot
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=20261019150704.1851215-1-dave.hansen@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®