From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Serial <linux-serial@vger.kernel.org>
Cc: "Cengiz Can" <cengiz@kernel.wtf>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"Tomas Mudrunka" <tomas.mudrunka@gmail.com>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Anselm Schüler" <mail@anselmschueler.com>,
"Randy Dunlap" <rdunlap@infradead.org>
Subject: Re: [PATCH v3] Documentation: sysrq: Rewrite /proc/sysrq-trigger usage
Date: Mon, 03 Nov 2025 16:33:20 -0700 [thread overview]
Message-ID: <87jz06bsjj.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251023014102.16777-1-bagasdotme@gmail.com>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> /proc/sysrq-trigger usage documentation (in "On all" section) states
> that it is not recommended to write extra characters to it. The sentence
> may imply a contradiction to previous sentence which writes that such
> characters are ignored.
>
> Rewrite the description.
>
> Link: https://lore.kernel.org/lkml/7ca05672-dc20-413f-a923-f77ce0a9d307@anselmschueler.com/
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Changes since v2 [1]:
>
> - Keep /proc/sysrq-trigger future API change note (Tomas)
>
> Anselm: Do you object to the rewrite?
It still seems confusing...
> [1]: https://lore.kernel.org/linux-doc/20251016103609.33897-2-bagasdotme@gmail.com/
>
> Documentation/admin-guide/sysrq.rst | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/admin-guide/sysrq.rst b/Documentation/admin-guide/sysrq.rst
> index 9c7aa817adc72d..a88266b171aa17 100644
> --- a/Documentation/admin-guide/sysrq.rst
> +++ b/Documentation/admin-guide/sysrq.rst
> @@ -75,16 +75,15 @@ On other
> submit a patch to be included in this section.
>
> On all
> - Write a single character to /proc/sysrq-trigger.
> - Only the first character is processed, the rest of the string is
> - ignored. However, it is not recommended to write any extra characters
> - as the behavior is undefined and might change in the future versions.
> - E.g.::
> + Write a single character to /proc/sysrq-trigger. E.g.::
>
> echo t > /proc/sysrq-trigger
>
> - Alternatively, write multiple characters prepended by underscore.
> - This way, all characters will be processed. E.g.::
> + Only the first character is processed; any following characters are
> + ignored for now, which might change in the future.
> +
> + Alternatively, to write multiple characters, prepend them with an
> + underscore so that these all will be processed. E.g.::
You're still saying that following characters are ignored, then give an
example where they are not:
> echo _reisub > /proc/sysrq-trigger
So, for me, this still isn't really right.
This, I think, is a holdover from before, but I have to point out that:
> echo t > /proc/sysrq-trigger
Does *not* write a single character: it writes "t\n".
jon
prev parent reply other threads:[~2025-11-03 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 1:41 Bagas Sanjaya
2025-10-23 4:42 ` Randy Dunlap
2025-11-03 23:33 ` Jonathan Corbet [this message]
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=87jz06bsjj.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--cc=cengiz@kernel.wtf \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mail@anselmschueler.com \
--cc=rdunlap@infradead.org \
--cc=tomas.mudrunka@gmail.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®