From: Alan Mackenzie <acm@muc.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, 34235@debbugs.gnu.org,
Eli Zaretskii <eliz@gnu.org>,
Alex Branham <alex.branham@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 (posix-timers: Fix division by zero bug). Problems with glibc.
Date: Sat, 2 Feb 2019 10:44:04 +0000 [thread overview]
Message-ID: <20190202104404.GA1067@ACM> (raw)
In-Reply-To: <alpine.DEB.2.21.1902012301310.8200@nanos.tec.linutronix.de>
Hello, Thomas.
Thanks for such a rapid reply!
On Fri, Feb 01, 2019 at 23:04:48 +0100, Thomas Gleixner wrote:
> Hello Alan,
> On Fri, 1 Feb 2019, Alan Mackenzie wrote:
> > 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94
> > posix-timers: Fix division by zero bug
> > Committed: 2018-12-17 17:35:45 +0100
> > With this patch in place I am seeing problems with glibc's function
> > timer_create. I am an Emacs maintainer, and saw these problems whilst
> > investigating Emacs bug #34235 "27.0.50; lisp profiler does not work".
> > Emacs's profiler fails in kernel 4.19.13, but works in a version of
> > 4.19.13 with the patch reversed, otherwise unchanged. My current version
> > of glibc is 2.27-r6 (I think the "-r6" comes from Gentoo, my distro).
> Please upgrade to 4.19.19. The issue should be fixed there with the
> backported variant of
> 93ad0fc088c5 ("posix-cpu-timers: Unbreak timer rearming")
> Commit 21c0d1621b8d4b in 4.19.19
I've just built and installed Linux 4.19.19, and it does indeed solve
the Emacs profiler bug, #34235. :-)
I see that the patch has been installed in 4.20.6, 4.19.19, and 4.14.97.
Are there any plans to install it into 4.9.x, the other live long term
support branch? The reason I ask is to make an entry into Emacs's
PROBLEMS file, telling users and distributions which kernel versions to
upgrade to.
> Thanks,
> tglx
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-02-02 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 21:47 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 (posix-timers: Fix division by zero bug). Problems with glibc Alan Mackenzie
2019-02-01 22:04 ` Thomas Gleixner
2019-02-02 10:44 ` Alan Mackenzie [this message]
2019-02-04 17:25 ` Thomas Gleixner
2019-02-05 13:54 ` Alan Mackenzie
-- strict thread matches above, loose matches on Subject: below --
2019-02-02 2:07 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 (posix-timers: Fix, " Paul Eggert
2019-02-02 9:21 ` Thomas Gleixner
2019-02-03 6:28 ` Paul Eggert
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=20190202104404.GA1067@ACM \
--to=acm@muc.de \
--cc=34235@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=eggert@cs.ucla.edu \
--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 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.