From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754265AbdEDNcg (ORCPT ); Thu, 4 May 2017 09:32:36 -0400 Received: from scorn.kernelslacker.org ([45.56.101.199]:39618 "EHLO scorn.kernelslacker.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754113AbdEDNc3 (ORCPT ); Thu, 4 May 2017 09:32:29 -0400 Date: Thu, 4 May 2017 09:32:25 -0400 From: Dave Jones To: Arun Raghavan Cc: Linux Kernel Mailing List , Thomas Gleixner , Linus Torvalds Subject: Re: rlimits: Print more information when CPU/RT limits are exceeded Message-ID: <20170504133225.jatemh6hy3xhvpk5@codemonkey.org.uk> Mail-Followup-To: Dave Jones , Arun Raghavan , Linux Kernel Mailing List , Thomas Gleixner , Linus Torvalds References: <20170501232152.8142E661220@gitolite.kernel.org> <20170502031230.jz5b6witmmujsdmq@codemonkey.org.uk> <1493872696.160584.965253552.34C536BA@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1493872696.160584.965253552.34C536BA@webmail.messagingengine.com> User-Agent: NeoMutt/20170306 (1.8.0) X-Spam-Note: SpamAssassin invocation failed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 04, 2017 at 10:08:16AM +0530, Arun Raghavan wrote: > On Tue, 2 May 2017, at 08:42 AM, Dave Jones wrote: > > On Mon, May 01, 2017 at 11:21:52PM +0000, Linux Kernel wrote: > > > Web: https://git.kernel.org/torvalds/c/e7ea7c9806a2681807257ea89085339d33f7fa0b > > > Commit: e7ea7c9806a2681807257ea89085339d33f7fa0b > > > Parent: 4495c08e84729385774601b5146d51d9e5849f81 > > > Refname: refs/heads/master > > > Author: Arun Raghavan > > > AuthorDate: Wed Mar 1 20:23:09 2017 +0530 > > > Committer: Thomas Gleixner > > > CommitDate: Mon Mar 13 21:32:15 2017 +0100 > > > > > > rlimits: Print more information when CPU/RT limits are exceeded > > > > > > When a process is sent a SIGKILL because it exceeded CPU or RT limits, > > > the cause may not be obvious in userspace -- daemonised processes just > > > get killed, and even foreground process just see a 'Killed' message. The > > > lack of any information on why this might be happening in logs can be > > > confusing to users who are not aware of this mechanism. > > > > > > Add messages which dump the process name and tid in dmesg when a process > > > exceeds its CPU or RT limits (soft and hard) in order to make it clearer to > > > people debugging such issues. > > > > > > Signed-off-by: Arun Raghavan > > > Link: http://lkml.kernel.org/r/20170301145309.27214-1-arun@arunraghavan.net > > > Signed-off-by: Thomas Gleixner > > > > This needs to be configurable, because this is really obnoxious.. > > Is there an example of hos this is done elsewhere that I can work off? The obvious one to me that comes to mind is /proc/sys/kernel/print-fatal-signals Dave