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]

Date:	Fri, 09 Feb 2007 16:25:11 +0100
From:	John <linux.kernel@...e.fr>
To:	linux-kernel@...r.kernel.org
CC:	Thomas Gleixner <tglx@...esys.com>, a.p.zijlstra@...llo.nl,
	mingo@...e.hu, johnstul@...ibm.com, akpm@...l.org
Subject: Re: One-shot high-resolution POSIX timer periodically late

Thomas Gleixner wrote:

> On Wed, 2007-02-07 at 11:25 +0100, John wrote:
> 
>> Are there people that use the -rt patch set in real industrial applications?
> 
> Yes. But we use a stabilized version of 2.6.16-rt29.
> http://www.osadl.org/projects/downloads/preempt-rt/linux-2.6.16/

Thanks for the pointer.

I'm confused: patch-2.6.16-rt29-tglx3 is dated 2006-09-07, yet there
have been numerous revisions of the -rt patch set since then. Does that
mean that no serious bugs have been found since September? Do the -rt
patch sets for 2.6.17 - 2.6.20 only bring new features and/or adapt the
-rt infrastructure to the newer kernels?

>> It seems that, if an important bug is found in the -rt part, I will have 
>> to either upgrade to the latest kernel, or back port all the -rt changes 
>> to the kernel I chose for my application?
> 
> Yep.

Ouch :-)

I think I'll try my luck with 2.6.20 (it's been working so far).

By the way, I have a question: when I compile glibc for this system,
should I compile it against the vanilla 2.6.20 includes, or against the
patched 2.6.20-rt includes?

Regards.


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