Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753646AbcCHDL1 (ORCPT <rfc822;w@1wt.eu>);
	Mon, 7 Mar 2016 22:11:27 -0500
Received: from mga01.intel.com ([192.55.52.88]:32311 "EHLO mga01.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753435AbcCHDLU (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 7 Mar 2016 22:11:20 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.22,554,1449561600"; 
   d="scan'208";a="928993225"
Date: Mon, 7 Mar 2016 19:11:19 -0800
From: Andi Kleen <ak@linux.intel.com>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hung task detector versus NFS (TASK_KILLABLE)
Message-ID: <20160308031119.GM23621@tassilo.jf.intel.com>
References: <20160307235944.GD15986@hostway.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160307235944.GD15986@hostway.ca>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 400
Lines: 11

> I write this because I would actually find it useful to see the original
> backtrace, even if it is interruptible, not just the collateral damage.
> Since the "skipping" of NFS is basically incomplete anyway, how big a
> deal is this "feature"?

Random backtrace spewing is always a misfeature for 99.99+% of the users
for whom it is gibberish.

If you really need it yourself add a kprobe.

-Andi