linux-kernel - commit 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 breaks timer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMe9rOq0K62wcXC76xn10Rb+Ry1p+M4wB5MCNA5QF9oUGZJZSA@mail.gmail.com>
Date:   Sun, 30 Dec 2018 18:07:23 -0800
From:   "H.J. Lu" <hjl.tools@...il.com>
To:     LKML <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: commit 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 breaks timer

On 4.19 branch,

commit 82c8dbb376b9fa9b831c157cbb15664cb4a343e3
Author: Thomas Gleixner <tglx@...utronix.de>
Date:   Mon Dec 17 13:31:05 2018 +0100

    posix-timers: Fix division by zero bug

    commit 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 upstream.

    The signal delivery path of posix-timers can try to rearm the timer even if
    the interval is zero. That's handled for the common case (hrtimer) but not
    for alarm timers. In that case the forwarding function raises a division by
    zero exception.

    The handling for hrtimer based posix timers is wrong because it marks the
    timer as active despite the fact that it is stopped.

    Move the check from common_hrtimer_rearm() to posixtimer_rearm() to cure
    both issues.

caused:

https://bugzilla.redhat.com/show_bug.cgi?id=1662602

-- 
H.J.