linux-kernel - Re: Issue in Kernel docs / Admin Guide / SysRq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aN_dLVPkwvxGM9R1@archie.me>
Date: Fri, 3 Oct 2025 21:26:53 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Anselm Schüler <mail@...elmschueler.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Documentation <linux-doc@...r.kernel.org>
Cc: Tomas Mudrunka <tomas.mudrunka@...il.com>,
	Jiri Slaby <jirislaby@...nel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: Issue in Kernel docs / Admin Guide / SysRq

On Fri, Oct 03, 2025 at 02:32:57PM +0200, Anselm Schüler wrote:
> I’m writing here because I don’t know where to find Kernel docs
> (https://docs.kernel.org/) sources and submit patches.
> 

It's in Documentation/ directory of kernel sources.

If you want to send docs patches, please read
Documentation/process/submitting-patches.rst for how to submit them and make
sure to Cc: linux-doc@...r.kernel.org.

> The page “Linux Magic System Request Key Hacks”
> (https://docs.kernel.org/admin-guide/sysrq.html) says this:
> 
> “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.:
>     echo t > /proc/sysrq-trigger”

I think that the second sentence refers to writing subsequent characters in
this context.

> 
> I interpret the command as a suggestion of how to properly use
> /proc/sysrq-trigger, and not as an example of what not to do, and I believe
> many will share this interpretation. The command as listed will write TWO
> characters to /proc/sysrq-trigger.
> 
> Either the behaviour of ignoring \n should be codified and explicitly
> supported or this section should be changed.
> 

See commit 39ff20f5fd4481 ("/proc/sysrq-trigger: accept multiple keys at
once").

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)