linux-kernel - Re: [RESEND PATCH 2/7] time: Change posix clocks ops interfaces to use timespec64

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: <alpine.DEB.2.20.1703202140000.3772@nanos>
Date:   Mon, 20 Mar 2017 21:40:52 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Deepa Dinamani <deepa.kernel@...il.com>
cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        John Stultz <john.stultz@...aro.org>,
        Arnd Bergmann <arnd@...db.de>,
        y2038 Mailman List <y2038@...ts.linaro.org>
Subject: Re: [RESEND PATCH 2/7] time: Change posix clocks ops interfaces to
 use timespec64

On Mon, 20 Mar 2017, Deepa Dinamani wrote:
> >> -static int ptp_clock_getres(struct posix_clock *pc, struct timespec *tp)
> >> +static int ptp_clock_getres(struct posix_clock *pc, struct timespec64 *tp)
> >
> > That's a pretty pointless exercise. getres() returns the resolution of the
> > clock which obviously can never be affected by Y2038.
> 
> True, tv_sec does not need to be more than 32 bits here.
> We plan to limit the use of struct timespec to existing user interfaces only.

This is an existing user space interface and there is no need to change it
at all.

Thanks,

	tglx