From: Ingo Molnar <mingo@kernel.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org,
gerlando.falauto@keymile.com, john.stultz@linaro.org,
minggr@gmail.com, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org, lttng-dev@lists.lttng.org
Subject: Re: [tip:timers/urgent] timekeeping: Fix HRTICK related deadlock from ntp lock changes
Date: Tue, 17 Sep 2013 09:07:28 +0200 [thread overview]
Message-ID: <20130917070728.GC20661@gmail.com> (raw)
In-Reply-To: <20130916160426.GA24669@Krystal>
* Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> Hi Ingo,
>
> Do you have an estimate of the time it will take for this fix to hit
> mainline, stable-3.10 and stable-3.11 ? Meanwhile, I'm marking 3.10 and
> 3.11 as broken for LTTng with a kernel version at compile-time, since
> this kernel regression currently triggers hard system lockup when people
> use LTTng on those kernels, and this is certainly something nobody
> wants.
So, at least as per the description of John, this should only trigger if
SCHED_HRTICK is enabled in sched_features - which is disabled by default,
it's a debug-only development feature. Does the bug trigger on more
regular kernels as well?
I planned to send it Linus after v3.12-rc1, in the next day or two.
Thanks,
Ingo
next prev parent reply other threads:[~2013-09-17 7:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1378943457-27314-1-git-send-email-john.stultz@linaro.org>
[not found] ` <tip-7bd36014460f793c19e7d6c94dab67b0afcfcb7f@git.kernel.org>
2013-09-16 16:04 ` [tip:timers/urgent] timekeeping: Fix HRTICK related deadlock from ntp lock changes Mathieu Desnoyers
2013-09-17 7:07 ` Ingo Molnar [this message]
2013-09-17 8:09 ` Mathieu Desnoyers
2013-09-17 8:26 ` Ingo Molnar
2013-09-17 16:33 ` Mathieu Desnoyers
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=20130917070728.GC20661@gmail.com \
--to=mingo@kernel.org \
--cc=gerlando.falauto@keymile.com \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=minggr@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).