From: Paul Eggert <eggert@cs.ucla.edu>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Alex Branham <alex.branham@gmail.com>,
Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>,
linux-kernel@vger.kernel.org, 34235@debbugs.gnu.org
Subject: Re: 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 (posix-timers: Fix, division by zero bug). Problems with glibc.
Date: Sat, 2 Feb 2019 22:28:49 -0800 [thread overview]
Message-ID: <1682db6c-0e70-f4d2-ecc7-6dabbccdcccc@cs.ucla.edu> (raw)
In-Reply-To: <alpine.DEB.2.21.1902021020020.8200@nanos.tec.linutronix.de>
Thomas Gleixner wrote:
> Can you please verify whether the issue is fixed with 4.19.19?
It depends on what you mean by "verify". I looked at the Linux kernel source
code and checked that the "posix-cpu-timers: Unbreak timer rearming" patch is in
4.19.19 (but not 4.19.18) and in 4.20.6 (but not 4.20.5). I did not test Emacs's
CPU profiler on these kernels, as I don't have them installed. I expect to
upgrade soon to 4.20.6 (whenever Fedora 29 release does - 4.20.6 was submitted
for testing a couple of days ago) and plan to give it a try then.
next prev parent reply other threads:[~2019-02-03 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 2:07 Paul Eggert
2019-02-02 9:21 ` Thomas Gleixner
2019-02-03 6:28 ` Paul Eggert [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-01 21:47 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 (posix-timers: Fix " Alan Mackenzie
2019-02-01 22:04 ` Thomas Gleixner
2019-02-02 10:44 ` Alan Mackenzie
2019-02-04 17:25 ` Thomas Gleixner
2019-02-05 13:54 ` Alan Mackenzie
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=1682db6c-0e70-f4d2-ecc7-6dabbccdcccc@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=34235@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=alex.branham@gmail.com \
--cc=eliz@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®