linux-kernel - Re: new warning on sysrq kernel crash trigger

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]

Message-ID: <566EF73C.3090505@redhat.com>
Date:	Mon, 14 Dec 2015 12:07:08 -0500
From:	Rik van Riel <riel@...hat.com>
To:	Ani Sinha <ani@...sta.com>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>
Cc:	Randy Dunlap <rdunlap@...radead.org>,
	Richard Weinberger <richard@....at>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ivan Delalande <colona@...sta.com>,
	fruggeri <fruggeri@...sta.com>
Subject: Re: new warning on sysrq kernel crash trigger

On 12/14/2015 11:24 AM, Ani Sinha wrote:
> Rik, any comments?

Another good option is to simply ignore this warning, or drop
the rcu_read_lock before doing the alt-syrsq-c action.

After all, alt-sysrq-c is "crash the system, take a crash dump",
which is not an action the system ever returns from.

static struct sysrq_key_op sysrq_crash_op = {
        .handler        = sysrq_handle_crash,
        .help_msg       = "crash(c)",
        .action_msg     = "Trigger a crash",
        .enable_mask    = SYSRQ_ENABLE_DUMP,
};

-- 
All rights reversed
--
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/