mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 11:00:41 +0800	[thread overview]
Message-ID: <aV3MWf005ja00BDU@U-2FWC9VHC-2323.local> (raw)
In-Reply-To: <20260106163321.83586-1-gal@nvidia.com>

Hi Gal,

Thanks for the fix!

On Tue, Jan 06, 2026 at 06:33:21PM +0200, Gal Pressman wrote:
> The panic_print_deprecated() warning is being triggered on both read and
> write operations to the panic_print parameter.
> 
> This causes spurious warnings when users run 'sysctl -a' to list all
> sysctl values, since that command reads /proc/sys/kernel/panic_print and
> triggers the deprecation notice.
> 
> Modify the handlers to only emit the deprecation warning when the
> parameter is actually being set:
> 
>  - sysctl_panic_print_handler(): check 'write' flag before warning.
>  - panic_print_get(): remove the deprecation call entirely.
> 
> This way, users are only warned when they actively try to use the
> deprecated parameter, not when passively querying system state.
> 
> Fixes: ee13240cd78b ("panic: add note that panic_print sysctl interface is deprecated")
> Fixes: 2683df6539cb ("panic: add note that 'panic_print' parameter is deprecated")
> Cc: Feng Tang <feng.tang@linux.alibaba.com>
> Reviewed-by: Mark Bloch <mbloch@nvidia.com>
> Reviewed-by: Nimrod Oren <noren@nvidia.com>
> Signed-off-by: Gal Pressman <gal@nvidia.com>
> ---
>  kernel/panic.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/panic.c b/kernel/panic.c
> index 0d52210a9e2b..0c20fcaae98a 100644
> --- a/kernel/panic.c
> +++ b/kernel/panic.c
> @@ -131,7 +131,8 @@ static int proc_taint(const struct ctl_table *table, int write,
>  static int sysctl_panic_print_handler(const struct ctl_table *table, int write,
>  			   void *buffer, size_t *lenp, loff_t *ppos)
>  {
> -	panic_print_deprecated();
> +	if (write)
> +		panic_print_deprecated();

This makes sense to me, as 'sysctl -a' is a very common usage.

>  	return proc_doulongvec_minmax(table, write, buffer, lenp, ppos);
>  }
>  
> @@ -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.

Thanks,
Feng

>  	return  param_get_ulong(val, kp);
>  }
>  
> -- 
> 2.40.1

  reply	other threads:[~2026-01-07  3:00 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 [this message]
2026-01-07  6:41   ` Gal Pressman
2026-01-07  7:20     ` Feng Tang
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=aV3MWf005ja00BDU@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®