From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
Kees Cook <keescook@chromium.org>, SeongJae Park <sj@kernel.org>,
Seth Jenkins <sethjenkins@google.com>,
Jann Horn <jannh@google.com>,
"Eric W . Biederman" <ebiederm@xmission.com>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
Tony Luck <tony.luck@intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PATCH 4.19 v2 07/15] ia64: make IA64_MCA_RECOVERY bool instead of tristate
Date: Thu, 2 Feb 2023 16:27:09 -0800 [thread overview]
Message-ID: <20230203002717.49198-8-ebiggers@kernel.org> (raw)
In-Reply-To: <20230203002717.49198-1-ebiggers@kernel.org>
From: Randy Dunlap <rdunlap@infradead.org>
commit dbecf9b8b8ce580f4e11afed9d61e8aa294cddd2 upstream.
In linux-next, IA64_MCA_RECOVERY uses the (new) function
make_task_dead(), which is not exported for use by modules. Instead of
exporting it for one user, convert IA64_MCA_RECOVERY to be a bool
Kconfig symbol.
In a config file from "kernel test robot <lkp@intel.com>" for a
different problem, this linker error was exposed when
CONFIG_IA64_MCA_RECOVERY=m.
Fixes this build error:
ERROR: modpost: "make_task_dead" [arch/ia64/kernel/mca_recovery.ko] undefined!
Link: https://lkml.kernel.org/r/20220124213129.29306-1-rdunlap@infradead.org
Fixes: 0e25498f8cd4 ("exit: Add and use make_task_dead.")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Suggested-by: Christoph Hellwig <hch@infradead.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Tony Luck <tony.luck@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
arch/ia64/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/ia64/Kconfig b/arch/ia64/Kconfig
index 8b4a0c1748c03..0d56b19b7511a 100644
--- a/arch/ia64/Kconfig
+++ b/arch/ia64/Kconfig
@@ -445,7 +445,7 @@ config ARCH_PROC_KCORE_TEXT
depends on PROC_KCORE
config IA64_MCA_RECOVERY
- tristate "MCA recovery from errors other than TLB."
+ bool "MCA recovery from errors other than TLB."
config PERFMON
bool "Performance monitor support"
--
2.39.1
next prev parent reply other threads:[~2023-02-03 0:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 0:27 [PATCH 4.19 v2 00/15] Backport oops_limit to 4.19 Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 01/15] sysctl: add a new register_sysctl_init() interface Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 02/15] panic: unset panic_on_warn inside panic() Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 03/15] exit: Add and use make_task_dead Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 04/15] objtool: Add a missing comma to avoid string concatenation Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 05/15] hexagon: Fix function name in die() Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 06/15] h8300: Fix build errors from do_exit() to make_task_dead() transition Eric Biggers
2023-02-03 0:27 ` Eric Biggers [this message]
2023-02-03 0:27 ` [PATCH 4.19 v2 08/15] exit: Put an upper limit on how often we can oops Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 09/15] exit: Expose "oops_count" to sysfs Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 10/15] exit: Allow oops_limit to be disabled Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 11/15] panic: Consolidate open-coded panic_on_warn checks Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 12/15] panic: Introduce warn_limit Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 13/15] panic: Expose "warn_count" to sysfs Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 14/15] docs: Fix path paste-o for /sys/kernel/warn_count Eric Biggers
2023-02-03 0:27 ` [PATCH 4.19 v2 15/15] exit: Use READ_ONCE() for all oops/warn limit reads Eric Biggers
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=20230203002717.49198-8-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sethjenkins@google.com \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).