All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Yu-cheng Yu <yu-cheng.yu@intel.com>
Subject: Re: commit 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 breaks timer
Date: Thu, 3 Jan 2019 08:53:11 -0800	[thread overview]
Message-ID: <CAMe9rOpvs4-06unwnkPaMuAR6Ks4N4UwfkzmxLBSU0Q_4cRAww@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOq0K62wcXC76xn10Rb+Ry1p+M4wB5MCNA5QF9oUGZJZSA@mail.gmail.com>

On Sun, Dec 30, 2018 at 6:07 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On 4.19 branch,
>
> commit 82c8dbb376b9fa9b831c157cbb15664cb4a343e3
> Author: Thomas Gleixner <tglx@linutronix.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
>

I opened:

https://bugzilla.kernel.org/show_bug.cgi?id=202123

-- 
H.J.

      reply	other threads:[~2019-01-03 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-31  2:07 commit 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 breaks timer H.J. Lu
2019-01-03 16:53 ` H.J. Lu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMe9rOpvs4-06unwnkPaMuAR6Ks4N4UwfkzmxLBSU0Q_4cRAww@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yu-cheng.yu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.