Message-ID: <1437550528.3106.107.camel@gmail.com>
Subject: Re: [PATCH] soft lockup: kill realtime threads before panic
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: =?ISO-8859-1?Q?J=F6rn?= Engel <joern@purestorage.com>
Cc: Spencer Baugh <sbaugh@catern.com>, Don Zickus <dzickus@redhat.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Ulrich Obergfell <uobergfe@redhat.com>, Ingo Molnar <mingo@kernel.org>,
        Andrew Jones <drjones@redhat.com>,
        chai wen <chaiw.fnst@cn.fujitsu.com>,
        Chris Metcalf <cmetcalf@ezchip.com>,
        Stephane Eranian <eranian@google.com>,
        open list <linux-kernel@vger.kernel.org>,
        Spencer Baugh <Spencer.baugh@purestorage.com>,
        Joern Engel <joern@logfs.org>
Date: Wed, 22 Jul 2015 09:35:28 +0200
In-Reply-To: <20150722063323.GE23662@Sligo.logfs.org>
References: <1437516477-30554-5-git-send-email-sbaugh@catern.com>
	 <1437539790.3106.42.camel@gmail.com>
	 <20150722051827.GD23662@Sligo.logfs.org>
	 <1437543708.3106.70.camel@gmail.com>
	 <20150722063323.GE23662@Sligo.logfs.org>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 784
Lines: 18

On Tue, 2015-07-21 at 23:33 -0700, Jörn Engel wrote:

> One could argue that killing the realtime thread is even better than
> panic, as things can restart with a blank slate even faster.  But the
> real benefit is that we get better debug data for the failing component.
> If we had a kernel bug, the backtrace would usually be sufficient to
> point fingers.  With a bonkers realtime thread, not so much.

If userspace wants a watchdog, it should train a userspace dog, not turn
the kernel watchdog into a userspace attack dog.

	-Mike

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