posix-cpu-timers: Prevent spuriously armed 0-value itimer

Bugzilla: http://bugzilla.redhat.com/2022896

commit 8cd9da85d2bd87ce889043e7b1735723dd10eb89
Author: Frederic Weisbecker <frederic@kernel.org>
Date:   Mon Sep 13 16:53:32 2021 +0200

    posix-cpu-timers: Prevent spuriously armed 0-value itimer

    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

Signed-off-by: Phil Auld <pauld@redhat.com>
This commit is contained in:
Phil Auld 2021-11-15 10:29:57 -05:00
parent 9262f1b540
commit 2e15fe4f76
1 changed files with 2 additions and 1 deletions

View File

@ -1404,7 +1404,8 @@ void set_process_cpu_timer(struct task_struct *tsk, unsigned int clkid,
}
}
*newval += now;
if (*newval)
*newval += now;
}
/*