Re: [Y2038] Question regarding support of old time interfaces beyond y2038

2019-03-07 Thread Joseph Myers
On Thu, 7 Mar 2019, Lukasz Majewski wrote: > > 1) We should be clear that most of these will continue to be supported > > as C library interfaces even if they are not system calls. Some of > > them are obsolete enough and/or rarely used enough that we might not > > bother (the older ways to set t

Re: [Y2038] Question regarding support of old time interfaces beyond y2038

2019-03-07 Thread Arnd Bergmann
On Thu, Mar 7, 2019 at 3:43 PM Lukasz Majewski wrote: > > On Thu, Mar 7, 2019 at 8:53 AM Lukasz Majewski wrote: > > > > On Tue, Mar 5, 2019 at 10:24 AM Lukasz Majewski > To be more specific: > > I'm thinking of settimeofday/gettimeofday syscalls. > > In the kernel we use internally do_sys_setti

Re: [Y2038] Question regarding support of old time interfaces beyond y2038

2019-03-07 Thread Lukasz Majewski
Hi Arnd, > On Thu, Mar 7, 2019 at 8:53 AM Lukasz Majewski wrote: > > > > Hi Zack, > > > > > On Tue, Mar 5, 2019 at 10:24 AM Lukasz Majewski > > > wrote: > > > > From other discussion [4] - regarding the following system > > > > calls: time, stime, gettimeofday, settimeofday, adjtimex, > > >

Re: [Y2038] Question regarding support of old time interfaces beyond y2038

2019-03-07 Thread Arnd Bergmann
On Thu, Mar 7, 2019 at 8:53 AM Lukasz Majewski wrote: > > Hi Zack, > > > On Tue, Mar 5, 2019 at 10:24 AM Lukasz Majewski wrote: > > > From other discussion [4] - regarding the following system calls: > > > time, stime, gettimeofday, settimeofday, adjtimex, nanosleep, > > > alarm, getitimer, seti

Re: [Y2038] Question regarding support of old time interfaces beyond y2038

2019-03-06 Thread Lukasz Majewski
Hi Zack, > On Tue, Mar 5, 2019 at 10:24 AM Lukasz Majewski wrote: > > From other discussion [4] - regarding the following system calls: > > time, stime, gettimeofday, settimeofday, adjtimex, nanosleep, > > alarm, getitimer, setitimer, select, utime, utimes, futimesat, and > > {old,new}{l,f,}sta

Re: [Y2038] Question regarding support of old time interfaces beyond y2038

2019-03-06 Thread Lukasz Majewski
Hi Arnd, > On Tue, Mar 5, 2019 at 4:24 PM Lukasz Majewski wrote: > > > > Dear Arnd, > > > > In your "playground" repository [1] (branch: y2038), the time > > functions (stime, settimeofday, etc) are not converted in Linux to > > be Y2038 aware (as for example clock_settime{64}() is). > > Corre

Re: [Y2038] Question regarding support of old time interfaces beyond y2038

2019-03-05 Thread Arnd Bergmann
On Tue, Mar 5, 2019 at 4:24 PM Lukasz Majewski wrote: > > Dear Arnd, > > In your "playground" repository [1] (branch: y2038), the time functions > (stime, settimeofday, etc) are not converted in Linux to be Y2038 aware > (as for example clock_settime{64}() is). Correct. FWIW, this is now merged i

Re: [Y2038] Question regarding support of old time interfaces beyond y2038

2019-03-05 Thread Ben Hutchings
On Tue, 2019-03-05 at 11:05 -0500, Zack Weinberg wrote: > > On Tue, Mar 5, 2019 at 10:24 AM Lukasz Majewski wrote: > > From other discussion [4] - regarding the following system calls: > >  time, stime, gettimeofday, settimeofday, adjtimex, nanosleep, alarm, > >  getitimer, setitimer, select, utim

Re: [Y2038] Question regarding support of old time interfaces beyond y2038

2019-03-05 Thread Zack Weinberg
On Tue, Mar 5, 2019 at 10:24 AM Lukasz Majewski wrote: > From other discussion [4] - regarding the following system calls: > time, stime, gettimeofday, settimeofday, adjtimex, nanosleep, alarm, > getitimer, setitimer, select, utime, utimes, futimesat, and > {old,new}{l,f,}stat{,64}. > > "These

[Y2038] Question regarding support of old time interfaces beyond y2038

2019-03-05 Thread Lukasz Majewski
Dear Arnd, In your "playground" repository [1] (branch: y2038), the time functions (stime, settimeofday, etc) are not converted in Linux to be Y2038 aware (as for example clock_settime{64}() is). I've also searched on the Internet and I've found some old discussions regarding them: SHA1: d33c57