From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32081 invoked by alias); 26 Apr 2009 23:45:18 -0000 Received: (qmail 31948 invoked by uid 48); 26 Apr 2009 23:45:05 -0000 Date: Sun, 26 Apr 2009 23:45:00 -0000 Message-ID: <20090426234505.31947.qmail@sourceware.org> From: "samuel dot thibault at ens-lyon dot org" To: glibc-bugs@sources.redhat.com In-Reply-To: <20081228205119.9690.hvengel@astound.net> References: <20081228205119.9690.hvengel@astound.net> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/9690] glibc time functionality broken with kernel 2.6.26 and later X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00167.txt.bz2 ------- Additional Comments From samuel dot thibault at ens-lyon dot org 2009-04-26 23:45 ------- Please do not mix two things: - the kernel now exposes nanoseconds instead of microseconds. That's a kernel ABI break. It is announced via a STA_NANO flag in timex.status, but still, old applications are broken when started under kernels >= 2.6.26. That's really a concern as it's not even easy to notice while it can irritate users (unstable ntp time). - the kernel now exposes a new tai field. That's not a kernel ABI break as it just takes a reserved room. To expose it to applications we however need to change the userland ABI. I'd really much rather see a kernel fix for the first issue: the kernel should report nanoseconds _only_ if userland requests it. And the case of a new application running with an old kernel _has_ to be taken care of as well. As for the second issue, see Ulrich's comment: just define a new version. See for instance the sched_setaffinity() function that has changed its ABI (and API too actually). -- What |Removed |Added ---------------------------------------------------------------------------- CC| |samuel dot thibault at ens- | |lyon dot org http://sourceware.org/bugzilla/show_bug.cgi?id=9690 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.