public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Anirban Sinha <ani@arista.com>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Richard Weinberger <richard@nod.at>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ivan Delalande <colona@arista.com>,
	fruggeri <fruggeri@arista.com>
Subject: Re: new warning on sysrq kernel crash trigger
Date: Wed, 16 Dec 2015 11:22:46 -0500	[thread overview]
Message-ID: <56718FD6.60509@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.10.1512141611530.4196@bs347.sjc.aristanetworks.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/14/2015 07:14 PM, Anirban Sinha wrote:
> 
> 
> On Mon, 14 Dec 2015, Rik van Riel wrote:
> 
>> 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.
>> 
> 
> Yea I thought about this idea previously but then discarded it
> thinking it would be too hacky. Here's the cooked up patch. I hope
> this can be approved for mainline soon (I'm on vacation and working
> just on this issue remotely) :
> 
> From 105ff3ffce380650b3d58b3594a9be47bd604b28 Mon Sep 17 00:00:00
> 2001 From: Ani Sinha <ani@arista.com> Date: Mon, 14 Dec 2015
> 14:55:08 -0800 Subject: [PATCH 1/1] Fix 'sleeping function called
> from invalid context' warning in sysrq generated crash.
> 
> Commit 984d74a72076a1 ("sysrq: rcu-ify __handle_sysrq") replaced
> spin_lock_irqsave() calls with rcu_read_lock() calls in sysrq.
> Since rcu_read_lock() does not disable preemption,
> faulthandler_disabled() in __do_page_fault() in x86/fault.c returns
> false. When the code later calls might_sleep() in the pagefault
> handler, we get the following warning:
> 
> BUG: sleeping function called from invalid context at
> ../arch/x86/mm/fault.c:1187 in_atomic(): 0, irqs_disabled(): 0,
> pid: 4706, name: bash Preemption disabled at:[<ffffffff81484339>]
> printk+0x48/0x4a
> 
> To fix this, we release the RCU read lock before we crash.
> 
> Tested this patch on linux 3.18 by booting off one of our boards.
> 
> Fixes: 984d74a72076a1 ("sysrq: rcu-ify __handle_sysrq")
> 
> Signed-off-by: Ani Sinha <ani@arista.com>

Reviewed-by: Rik van Riel <riel@redhat.com>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWcY++AAoJEM553pKExN6DMsEIAIgRI2dlnimHDR30BWhAhj1m
rPlG3zEKsilR5/MjD3y/LZqIqG2PmMEpIGajeTOu5O9cZhIyon/6snHTST36kN2Y
2CMCdUYNTQtDLpg8RoFsu8cvL4gBdi4J+o/U4E8gFXn6MqNsk3U0Dow/BJl1dPAm
V2/aN2K6od3+HU0q3ZJGfcnc4SipkAnA3nmrh5OntXLtZBfye6ge7UONxLzBI2vR
+7sGTd3ebKd9AZlYevZQxnSaeJbikGJoCwreqMVTueX8fbhvvReo/f6OfnXF6HaF
vDK6lle/BFuHYb11/cWonSuKcphpAOfvX+n90BtbBMedUKNlGvLBBH55feIbOpw=
=BP+x
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2015-12-16 16:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 23:57 new warning on sysrq kernel crash trigger Ani Sinha
2015-12-11  5:26 ` Paul E. McKenney
2015-12-11 18:50   ` Ani Sinha
2015-12-11 20:44   ` Ani Sinha
2015-12-11 21:25     ` Paul E. McKenney
2015-12-11 22:10     ` Rik van Riel
2015-12-11 22:27       ` Paul E. McKenney
2015-12-11 23:41         ` Ani Sinha
2015-12-12  0:02           ` Paul E. McKenney
2015-12-12  0:11             ` Ani Sinha
2015-12-12  0:16         ` Ani Sinha
2015-12-12  1:03           ` Paul E. McKenney
2015-12-14 16:24             ` Ani Sinha
2015-12-14 17:07               ` Rik van Riel
2015-12-15  0:14                 ` Anirban Sinha
2015-12-16  0:52                   ` Ani Sinha
2015-12-16 16:25                     ` Rik van Riel
2015-12-17 17:28                       ` Greg KH
2015-12-18  1:18                         ` Ani Sinha
2015-12-16 16:22                   ` Rik van Riel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56718FD6.60509@redhat.com \
    --to=riel@redhat.com \
    --cc=ani@arista.com \
    --cc=colona@arista.com \
    --cc=fruggeri@arista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rdunlap@infradead.org \
    --cc=richard@nod.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox