From: Eric Biggers <ebiggers@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>, Baoquan He <bhe@redhat.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH] kernel/crash: Remove inclusion of crypto/sha1.h
Date: Sat, 14 Mar 2026 13:42:43 -0700 [thread overview]
Message-ID: <20260314204243.45001-1-ebiggers@kernel.org> (raw)
Several files related to kernel crash dumps include crypto/sha1.h but
never use any of its functionality. Remove these includes so that these
files don't unnecessarily come up in searches for which kernel code is
still using the obsolete SHA-1 algorithm.
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
---
kernel/crash_core.c | 2 --
kernel/crash_reserve.c | 2 --
kernel/vmcore_info.c | 2 --
3 files changed, 6 deletions(-)
diff --git a/kernel/crash_core.c b/kernel/crash_core.c
index 2c1a3791e4101..4f21fc3b108b8 100644
--- a/kernel/crash_core.c
+++ b/kernel/crash_core.c
@@ -25,12 +25,10 @@
#include <linux/panic.h>
#include <asm/page.h>
#include <asm/sections.h>
-#include <crypto/sha1.h>
-
#include "kallsyms_internal.h"
#include "kexec_internal.h"
/* Per cpu memory for storing cpu states in case of system crash. */
note_buf_t __percpu *crash_notes;
diff --git a/kernel/crash_reserve.c b/kernel/crash_reserve.c
index 62e60e0223cff..eee37a11380ce 100644
--- a/kernel/crash_reserve.c
+++ b/kernel/crash_reserve.c
@@ -18,12 +18,10 @@
#include <linux/crash_reserve.h>
#include <asm/page.h>
#include <asm/sections.h>
-#include <crypto/sha1.h>
-
#include "kallsyms_internal.h"
#include "kexec_internal.h"
/* Location of the reserved area for the crash kernel */
struct resource crashk_res = {
diff --git a/kernel/vmcore_info.c b/kernel/vmcore_info.c
index 8d82913223a13..36772126385ce 100644
--- a/kernel/vmcore_info.c
+++ b/kernel/vmcore_info.c
@@ -16,12 +16,10 @@
#include <linux/kmemleak.h>
#include <asm/page.h>
#include <asm/sections.h>
-#include <crypto/sha1.h>
-
#include "kallsyms_internal.h"
#include "kexec_internal.h"
/* vmcoreinfo stuff */
unsigned char *vmcoreinfo_data;
base-commit: 1c9982b4961334c1edb0745a04cabd34bc2de675
--
2.53.0
reply other threads:[~2026-03-14 20:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260314204243.45001-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@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.