From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-68222-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 124225 invoked by alias); 20 Mar 2016 08:07:09 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 124176 invoked by uid 89); 20 Mar 2016 08:07:05 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=cordialement, albert, Albert, H*M:albert
X-HELO: smtp2-g21.free.fr
Date: Sun, 20 Mar 2016 08:07:00 -0000
From: Albert ARIBAUD <albert.aribaud@3adev.fr>
To: Arnd Bergmann <arnd@arndb.de>
Cc: libc-alpha@sourceware.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: Second draft of the Y2038 design document
Message-ID: <20160320090647.08bbf778.albert.aribaud@3adev.fr>
In-Reply-To: <4221114.vu6KX3Ybkh@wuerfel>
References: <20160128204114.6c7dbbf7.albert.aribaud@3adev.fr>
	<1683528.yWvM1WbPg0@wuerfel>
	<56AAAE6E.3040607@cs.ucla.edu>
	<4221114.vu6KX3Ybkh@wuerfel>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2016-03/txt/msg00502.txt.bz2

Hi Arnd and Paul,

Le Fri, 29 Jan 2016 09:58:16 +0100, Arnd Bergmann <arnd@arndb.de> a
=C3=A9crit :

> On Thursday 28 January 2016 16:12:30 Paul Eggert wrote:
> > On 01/28/2016 03:21 PM, Arnd Bergmann wrote:
> > >> Why are struct rusage, getrusage, etc. Y2038-sensitive? They hold
> > >> >intervals, not absolute times.
> > > It can theoretically still overflow, though not at the same time:
> >=20
> > In that case, I don't understand why nanosleep, setitimer, adjtime,=20
> > pselect, etc. are not marked as Y2038-sensitive, as they can all=20
> > overflow a 32-bit time_t in the same way that getrusage can.
>=20
> Agreed. As Joseph said earlier, it does not really matter whether
> the interface is problematic by itself. If anything uses a time_t,
> it has to be changed along with everything else based on the
> definition of that type.

Thanks for the feedback (and sorry I could not reply earlier). I will
update the list accordingly.

Cordialement,
Albert ARIBAUD
3ADEV