Laura Abbott c3bca5d450 posix-cpu-timers: Ensure set_process_cpu_timer is always evaluated ... Commit a9445e47d8 ("posix-cpu-timers: Make set_process_cpu_timer() more robust") moved the check into the 'if' statement. Unfortunately, it did so on the right side of an && which means that it may get short circuited and never evaluated. This is easily reproduced with: $ cat loop.c void main() { struct rlimit res; /* set the CPU time limit */ getrlimit(RLIMIT_CPU,&res); res.rlim_cur = 2; res.rlim_max = 2; setrlimit(RLIMIT_CPU,&res); while (1); } Which will hang forever instead of being killed. Fix this by pulling the evaluation out of the if statement but checking the return value instead. Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1568337 Fixes: a9445e47d8 ("posix-cpu-timers: Make set_process_cpu_timer() more robust") Signed-off-by: Laura Abbott <labbott@redhat.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: stable@vger.kernel.org Cc: "Max R . P . Grossmann" <m@max.pm> Cc: John Stultz <john.stultz@linaro.org> Link: https://lkml.kernel.org/r/20180417215742.2521-1-labbott@redhat.com		2018-04-19 12:54:57 +02:00
..
Kconfig	…
Makefile	…
alarmtimer.c	…
clockevents.c	…
clocksource.c	…
hrtimer.c	…
itimer.c	…
jiffies.c	…
ntp.c	…
ntp_internal.h	…
posix-clock.c	…
posix-cpu-timers.c	posix-cpu-timers: Ensure set_process_cpu_timer is always evaluated	2018-04-19 12:54:57 +02:00
posix-stubs.c	…
posix-timers.c	…
posix-timers.h	…
sched_clock.c	…
test_udelay.c	…
tick-broadcast-hrtimer.c	…
tick-broadcast.c	…
tick-common.c	…
tick-internal.h	…
tick-oneshot.c	clockevents: Fix kernel messages split across multiple lines	2018-04-17 17:18:04 +02:00
tick-sched.c	…
tick-sched.h	…
time.c	…
timeconst.bc	…
timeconv.c	…
timecounter.c	…
timekeeping.c	timekeeping: Remove __current_kernel_time()	2018-04-17 17:18:05 +02:00
timekeeping.h	…
timekeeping_debug.c	…
timekeeping_internal.h	…
timer.c	…
timer_list.c	…