From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
corbet@lwn.net, mcgrof@kernel.org, keescook@chromium.org,
yzaikin@google.com, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, linux@rasmusvillemoes.dk,
ebiggers@google.com, peterz@infradead.org, ying.huang@intel.com,
mchehab+huawei@kernel.org, Jason@zx2c4.com, daniel@iogearbox.net,
robh@kernel.org, wangqing@vivo.com, prestwoj@gmail.com,
dsahern@kernel.org, stephen.s.brennan@oracle.com
Subject: Re: [RFC 0/1] Add sysctl entry for controlling crash_kexec_post_notifiers
Date: Sat, 2 Apr 2022 11:01:51 -0300 [thread overview]
Message-ID: <f2fe220f-70c9-7b95-a9cb-4709752e4bdc@igalia.com> (raw)
In-Reply-To: <20220401202300.12660-1-alejandro.j.jimenez@oracle.com>
On 01/04/2022 17:22, Alejandro Jimenez wrote:
> I noticed that in contrast to other kernel core parameters (e.g. kernel.panic,
> kernel.panic_on_warn, kernel.panic_print) crash_kexec_post_notifiers is not
> available as a sysctl tunable. I am aware that because it is a kernel core
> parameter, there is already an entry under:
>
> /sys/module/kernel/parameters/crash_kexec_post_notifiers
>
> and that allows us to read/modify it at runtime. However, I thought it should
> also be available via sysctl, since users that want to read/set this value at
> runtime might look there first.
>
> I believe there is an ongoing effort to clean up kernel/sysctl.c, but it wasn't
> clear to me if this entry (and perhaps the other panic related entries too)
> should be placed on kernel/panic.c. I wanted to verify first that this change
> would be welcomed before doing additional refactoring work.
>
> I'd appreciate any comments or suggestions.
>
> Thank you,
> Alejandro
Hi Alejandro, thanks for you patch. I have a "selfish" concern though,
I'll expose it here.
I'm working a panic refactor, in order to split the panic notifiers in
more lists - good summary of this discussion at [0].
I'm in the half of the patches, hopefully next 2 weeks I have something
ready to submit (I'll be out next week).
As part of this effort, I plan to have a more fine-grained control of
this parameter, and it's going to be a sysctl, but not
"crash_kexec_post_notifiers" - this one should be kept I guess due to
retro-compatibility, but it'd be a layer on top oh the new one.
With that said, unless you have urgent needs for this patch to be
reviewed/merged , I'd like to ask you to wait the series and I can loop
you there, so you may review/comment and see if it fits your use case.
Thanks,
Guilherme
[0] https://lore.kernel.org/lkml/YfPxvzSzDLjO5ldp@alley/
next prev parent reply other threads:[~2022-04-02 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 20:22 Alejandro Jimenez
2022-04-01 20:23 ` [RFC 1/1] kernel/sysctl: Add sysctl entry for crash_kexec_post_notifiers Alejandro Jimenez
2022-04-01 21:35 ` Luis Chamberlain
2022-04-02 14:01 ` Guilherme G. Piccoli [this message]
2022-04-04 20:43 ` [RFC 0/1] Add sysctl entry for controlling crash_kexec_post_notifiers Alejandro Jimenez
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=f2fe220f-70c9-7b95-a9cb-4709752e4bdc@igalia.com \
--to=gpiccoli@igalia.com \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=alejandro.j.jimenez@oracle.com \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=dsahern@kernel.org \
--cc=ebiggers@google.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mcgrof@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=peterz@infradead.org \
--cc=prestwoj@gmail.com \
--cc=robh@kernel.org \
--cc=stephen.s.brennan@oracle.com \
--cc=wangqing@vivo.com \
--cc=ying.huang@intel.com \
--cc=yzaikin@google.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®