aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/time/hrtimer.c
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2019-08-29 12:52:28 +0200
committerThomas Gleixner <tglx@linutronix.de>2019-08-29 12:52:28 +0200
commita2ed4fd685cd23e98922f933d5dbccfbe82a4f08 (patch)
tree709002a36f11645816a152a971c9f54a6c95480a /kernel/time/hrtimer.c
parentposix-timers: Unbreak CONFIG_POSIX_TIMERS=n build (diff)
downloadlinux-dev-a2ed4fd685cd23e98922f933d5dbccfbe82a4f08.tar.xz
linux-dev-a2ed4fd685cd23e98922f933d5dbccfbe82a4f08.zip
posix-cpu-timers: Make expiry_active check actually work correctly
The state tracking changes broke the expiry active check by not writing to it and instead sitting timers_active, which is already set. That's not a big issue as the actual expiry is protected by sighand lock, so concurrent handling is not possible. That means that the second task which invokes that function executes the expiry code for nothing. Write to the proper flag. Also add a check whether the flag is set into check_process_timers(). That check had been missing in the code before the rework already. The check for another task handling the expiry of process wide timers was only done in the fastpath check. If the fastpath check returns true because a per task timer expired, then the checking of process wide timers was done in parallel which is as explained above just a waste of cycles. Fixes: 244d49e30653 ("posix-cpu-timers: Move state tracking to struct posix_cputimers") Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Frederic Weisbecker <frederic@kernel.org>
Diffstat (limited to 'kernel/time/hrtimer.c')
0 files changed, 0 insertions, 0 deletions