Revision 8cd9da85d2bd87ce889043e7b1735723dd10eb89 authored by Frederic Weisbecker on 13 September 2021, 14:53:32 UTC, committed by Thomas Gleixner on 23 September 2021, 09:53:51 UTC
Resetting/stopping an itimer eventually leads to it being reprogrammed with an actual "0" value. As a result the itimer expires on the next tick, triggering an unexpected signal. To fix this, make sure that struct signal_struct::it[CPUCLOCK_PROF/VIRT]::expires is set to 0 when setitimer() passes a 0 it_value, indicating that the timer must stop. Fixes: 406dd42bd1ba ("posix-cpu-timers: Force next expiration recalc after itimer reset") Reported-by: Victor Stinner <vstinner@redhat.com> Reported-by: Chris Hixon <linux-kernel-bugs@hixontech.com> Signed-off-by: Frederic Weisbecker <frederic@kernel.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Link: https://lore.kernel.org/r/20210913145332.232023-1-frederic@kernel.org
1 parent e4e737b
File | Mode | Size |
---|---|---|
.gitignore | -rw-r--r-- | 53 bytes |
Kconfig | -rw-r--r-- | 761 bytes |
Makefile | -rw-r--r-- | 584 bytes |
bpfilter_kern.c | -rw-r--r-- | 2.8 KB |
bpfilter_umh_blob.S | -rw-r--r-- | 196 bytes |
main.c | -rw-r--r-- | 1.1 KB |
msgfmt.h | -rw-r--r-- | 238 bytes |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...