From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752315AbbLNRHX (ORCPT ); Mon, 14 Dec 2015 12:07:23 -0500 Received: from mx1.redhat.com ([209.132.183.28]:38739 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751057AbbLNRHW (ORCPT ); Mon, 14 Dec 2015 12:07:22 -0500 Subject: Re: new warning on sysrq kernel crash trigger To: Ani Sinha , Paul McKenney References: <20151211052647.GL28602@linux.vnet.ibm.com> <566B49E3.1080107@redhat.com> <20151211222742.GJ4054@linux.vnet.ibm.com> <20151212010344.GR4054@linux.vnet.ibm.com> Cc: Randy Dunlap , Richard Weinberger , "linux-kernel@vger.kernel.org" , Ivan Delalande , fruggeri From: Rik van Riel Message-ID: <566EF73C.3090505@redhat.com> Date: Mon, 14 Dec 2015 12:07:08 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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