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] [day] [month] [year] [list]
Message-ID: <CABeXuvrvPB85rf7tjmMOotofRFv+NkN4CH0C6cPZJAVc-dBQqg@mail.gmail.com>
Date:   Tue, 1 Aug 2017 15:38:00 -0700
From:   Deepa Dinamani <deepa.kernel@...il.com>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Al Viro <viro@...iv.linux.org.uk>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
        y2038 Mailman List <y2038@...ts.linaro.org>
Subject: Re: [PATCH v2 4/6] ipc: sem: Make sem_array timestamps y2038 safe

> Unless I'm missing something here, you can drop the cast to
> unsigned long long: time64_t is always 'long long' and won't
> cause a warning here.
>
> We only need a cast like this when printing the members of 'struct
>  timespec64', since that can be either 'long long' or 'long', when
> it is defined as an alias for timespec.

You are right.
I think I had timespec64 on my mind when I added this cast.
I will update the series with the casts removed.

Thanks,
Deepa

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ