summaryrefslogtreecommitdiffstats
path: root/Documentation/fault-injection
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2019-08-21 21:09:18 +0200
committerThomas Gleixner <tglx@linutronix.de>2019-08-28 11:50:40 +0200
commit24db4dd90dd53ad6e3331b6f01cb985e466cface (patch)
tree8fa82b8396f2ff24425784ffb5cc67463495fa62 /Documentation/fault-injection
parentfe0517f893d36636de20d0a809fc0c788ca0cade (diff)
downloadlinux-24db4dd90dd53ad6e3331b6f01cb985e466cface.tar.gz
linux-24db4dd90dd53ad6e3331b6f01cb985e466cface.tar.bz2
linux-24db4dd90dd53ad6e3331b6f01cb985e466cface.zip
rlimit: Rewrite non-sensical RLIMIT_CPU comment
The comment above the function which arms RLIMIT_CPU in the posix CPU timer code makes no sense at all. It claims that the kernel does not return an error code when it rejected the attempt to set RLIMIT_CPU. That's clearly bogus as the code does an error check and the rlimit is only set and activated when the permission checks are ok. In case of a rejection an appropriate error code is returned. This is a historical and outdated comment which got dragged along even when the rlimit handling code was rewritten. Replace it with an explanation why the setup function is not called when the rlimit value is RLIM_INFINITY and how the 'disarming' is handled. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Frederic Weisbecker <frederic@kernel.org> Link: https://lkml.kernel.org/r/20190821192922.185511287@linutronix.de
Diffstat (limited to 'Documentation/fault-injection')
0 files changed, 0 insertions, 0 deletions