[lkml]   [2019]   [Aug]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch V2 31/38] rlimit: Rewrite non-sensical RLIMIT_CPU comment
On Wed, Aug 21, 2019 at 09:09:18PM +0200, Thomas Gleixner wrote:
> 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 <>
> Cc: Andrew Morton <>
> Cc: Jiri Slaby <>

Reviewed-by: Frederic Weisbecker <>

 \ /
  Last update: 2019-08-26 23:43    [W:0.236 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site