linux-kernel - Re: [PATCH] /proc/sysrq-trigger can now pause processing for one second

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: <CAH2-hc+OeJw6mZbekqCLF33GPY5wCHRMhS7auGMmR=dFazwG+w@mail.gmail.com>
Date: Mon, 18 Dec 2023 13:53:16 +0100
From: Tomáš Mudruňka <tomas.mudrunka@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-serial@...r.kernel.org
Subject: Re: [PATCH] /proc/sysrq-trigger can now pause processing for one second

> Add pauses and soon you will want loops and then it's turing complete :)
>
> Why not have a bpf script that does this instead?  :)

Funny you mention this. For a moment i've actually thought someone
would come with this idea sooner or later. :-)
But i think we will all agree that there are several reasons why this
would be quite terrible idea...

Anyway for me the sysrq-trigger is about giving kernel linear
instructions on how to shutdown/reboot ASAP with minimal chance for
data corruption and least amount of userspace involvement possible. I
just want to kill everything more or less cleanly and safely reboot
without having to give control back to userspace script, because there
might be something wrong with userspace at the time.

Tom