diff options
| author | Arun Raghavan <arun@arunraghavan.net> | 2017-03-01 17:53:09 +0300 |
|---|---|---|
| committer | Thomas Gleixner <tglx@linutronix.de> | 2017-03-13 23:32:15 +0300 |
| commit | e7ea7c9806a2681807257ea89085339d33f7fa0b (patch) | |
| tree | 10c31f31e93c29475e2a443db27109238f89aa6b /include | |
| parent | 4495c08e84729385774601b5146d51d9e5849f81 (diff) | |
| download | linux-e7ea7c9806a2681807257ea89085339d33f7fa0b.tar.xz | |
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 <arun@arunraghavan.net>
Link: http://lkml.kernel.org/r/20170301145309.27214-1-arun@arunraghavan.net
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions