linux-kernel - Re: [PATCH 6/7] time: move old timekeeping interfaces to timekeeping32.h

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:   Tue, 24 Oct 2017 12:57:42 -0700
From:   John Stultz <john.stultz@...aro.org>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        y2038 Mailman List <y2038@...ts.linaro.org>,
        Deepa Dinamani <deepa.kernel@...il.com>,
        Stephen Boyd <sboyd@...eaurora.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 6/7] time: move old timekeeping interfaces to timekeeping32.h

On Thu, Oct 19, 2017 at 4:14 AM, Arnd Bergmann <arnd@...db.de> wrote:
> The interfaces based on 'struct timespec' and 'unsigned long' seconds
> are no longer recommended for new code, and we are trying to migrate to
> ktime_t based interfaces and other y2038-safe variants.
>
> This moves all the legacy interfaces from linux/timekeeping.h into a
> new timekeeping32.h to better document this.
>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>

Just as a heads up, trying to apply these for testing (initially
against 4.14-rc3, but also -rc6) and I'm running into fuzz issues from
this patch on.

patch seems to resolve it, but not sure exactly what it was based on,
and wanted to make sure I'm not doing something daft.

thanks
-john