From: Feng Tang <feng.tang@linux.alibaba.com>
To: Gal Pressman <gal@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
linux-kernel@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
Nimrod Oren <noren@nvidia.com>
Subject: Re: [PATCH] panic: only warn about deprecated panic_print on write access
Date: Wed, 7 Jan 2026 15:20:44 +0800 [thread overview]
Message-ID: <aV4JTGkMTMTbcT1p@U-2FWC9VHC-2323.local> (raw)
In-Reply-To: <b280db0e-f1f7-41b5-887c-3b7b847ba035@nvidia.com>
On Wed, Jan 07, 2026 at 08:41:22AM +0200, Gal Pressman wrote:
> On 07/01/2026 5:00, Feng Tang wrote:
> >> @@ -1014,7 +1015,6 @@ static int panic_print_set(const char *val, const struct kernel_param *kp)
> >>
> >> static int panic_print_get(char *val, const struct kernel_param *kp)
> >> {
> >> - panic_print_deprecated();
> >
> > Actually this was intentional, in one of the patch version, this
> > panic_print_get() was not there but reusing the param_get_ulong().
> >
> > It was added later as sometimes developer do want to runtime check
> > the current 'panic_print' setting through /sys/module/kernel/parameters/
> > interface, and I thought it may be better to give the warning.
>
> I figured it would make sense to keep the behaviors consistent.
When people run 'sysctl -a', in 99.9% cases, the users don't care
'panic_print' or even don't know what 'panic_print' is, that's why
I think removing it makes sense.
But for a user running 'cat /sys/module/kernel/parameters/panic_rint',
giving a warning is meaningful.
If you insist so, the cleaner way would be
diff --git a/kernel/panic.c b/kernel/panic.c
index 0d52210a9e2b..86b927a695a0 100644
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -1012,15 +1012,9 @@ static int panic_print_set(const char *val, const struct kernel_param *kp)
return param_set_ulong(val, kp);
}
-static int panic_print_get(char *val, const struct kernel_param *kp)
-{
- panic_print_deprecated();
- return param_get_ulong(val, kp);
-}
-
static const struct kernel_param_ops panic_print_ops = {
.set = panic_print_set,
- .get = panic_print_get,
+ .get = param_get_ulong,
};
__core_param_cb(panic_print, &panic_print_ops, &panic_print, 0644);
next prev parent reply other threads:[~2026-01-07 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 16:33 Gal Pressman
2026-01-07 3:00 ` Feng Tang
2026-01-07 6:41 ` Gal Pressman
2026-01-07 7:20 ` Feng Tang [this message]
2026-01-08 15:52 ` Petr Mladek
2026-01-11 8:28 ` Gal Pressman
2026-01-12 3:32 ` Feng Tang
2026-01-12 6:48 ` Gal Pressman
2026-01-12 15:03 ` Petr Mladek
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=aV4JTGkMTMTbcT1p@U-2FWC9VHC-2323.local \
--to=feng.tang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=gal@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=noren@nvidia.com \
--cc=pmladek@suse.com \
/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®