linux-kernel - Re: One-shot high-resolution POSIX timer periodically late

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1170747081.4672.11.camel@twins>
Date:	Tue, 06 Feb 2007 08:31:21 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	John <shill@...e.fr>
Cc:	linux-kernel@...r.kernel.org, tglx@...esys.com, mingo@...e.hu,
	johnstul@...ibm.com, akpm@...l.org
Subject: Re: One-shot high-resolution POSIX timer periodically late

On Mon, 2007-02-05 at 17:37 +0100, John wrote:
> Ingo Molnar wrote:
> 
> > John wrote:
> > 
> >> John Stultz wrote:
> >> 
> >>> Also do check the -rt tree as Ingo suggested. I mis-read your earlier
> >>> email and thought you were running it.
> >> 
> >> I've been pulling my hair over a related issue for the past two days.
> >> 
> >> (I think I may be tickling a -hrt bug...)
> >> 
> >> I'm working with 2.6.18.6 + patch-2.6.18-rt7
> > 
> > 2.6.18-rt7 is pretty old, do you see the problem in 2.6.20-rc6-rt5 too?
> 
> Ingo, Thomas,
> 
> As far as I can tell, the -rt patch set is only updated for the latest 
> kernel version available. Is that correct?
> 
> http://people.redhat.com/mingo/realtime-preempt/older/?M=D
> 
> In other words, once 2.6.20 is released, and work starts on 2.6.21, if a 
> bug is discovered in -rt, the fix will not be back-ported to the 
> 2.6.20.x (and 2.6.19.x, and 2.6.18.x, etc) patch set?

Correct, there is only 1 live branch.

-
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/