linux-kernel - Re: [PATCH] sysrq: add debug message to reboot event

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 20 Aug 2009 15:10:24 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"tina.yang" <tina.yang@...cle.com>
Cc:	jkosina@...e.cz, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sysrq: add debug message to reboot event

On Wed, 19 Aug 2009 19:22:16 -0700
"tina.yang" <tina.yang@...cle.com> wrote:

> Add debug message to detect keyboard vs non-keyboard triggered sysrq-b events.
> This is to assist postmortem debugging on complicated computing setup with
> large number of applications involved where reboot event had occurred, but 
> unclear of its origin.

I'm still struggling to understand the motivation for the change. 
There are a large number of ways in which a machine can be rebooted,
all the way down to a triple-fault.  So it seems fairly arbitrary to
add additional information to discriminate between just two of those
ways.

I assume that somewhere in your setup you have a script which does
`echo b /proc/sysrq-trigger' and it took ages to work out that this was
happening and you felt that having this code in place would have
helped you debug that problem, yes?

If so, I wonder what is the likelihood that someone else will have the
same problem and will find this change useful.

Perhaps we should do this for all sysrq events rather than just sysrq-b?

> --- linux-2.6.18.i686/drivers/char/sysrq.c.orig	2009-08-13 10:55:57.526459000 -0700
> +++ linux-2.6.18.i686/drivers/char/sysrq.c	2009-08-13 10:58:10.798739000 -0700

2.6.18 is truly ancient and this patch doesn't apply at all to
current development kernels.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/