| 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
| ||
|
Date: Tue, 17 Sep 2013 09:07:28 +0200 From: Ingo Molnar <mingo@...nel.org> To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com> Cc: hpa@...or.com, linux-kernel@...r.kernel.org, gerlando.falauto@...mile.com, john.stultz@...aro.org, minggr@...il.com, tglx@...utronix.de, linux-tip-commits@...r.kernel.org, lttng-dev@...ts.lttng.org Subject: Re: [tip:timers/urgent] timekeeping: Fix HRTICK related deadlock from ntp lock changes * Mathieu Desnoyers <mathieu.desnoyers@...icios.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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists