linux-kernel - Re: [Y2038] [PATCH v2 03/10] compat: enable compat_get/put

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]

Date:   Sun, 7 Jan 2018 08:28:53 -0800
From:   Deepa Dinamani <deepa.kernel@...il.com>
To:     Ben Hutchings <ben.hutchings@...ethink.co.uk>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        John Stultz <john.stultz@...aro.org>,
        y2038 Mailman List <y2038@...ts.linaro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: [Y2038] [PATCH v2 03/10] compat: enable compat_get/put_timespec64 always

On Thu, Dec 14, 2017 at 3:27 PM, Ben Hutchings
<ben.hutchings@...ethink.co.uk> wrote:
> On Mon, 2017-11-27 at 11:30 -0800, Deepa Dinamani wrote:
>> These functions are used in the repurposed compat syscalls
>> to provide backward compatibility for using 32 bit time_t
>> on 32 bit systems.
>>
>> Signed-off-by: Deepa Dinamani <deepa.kernel@...il.com>
> [...]
>
> If I'm not mistaken, these functions will be needed only if
> CONFIG_COMPAT_32BIT_TIME is enabled.  Should this be combined with
> patch #5?

This was purposely decided to be included unconditionally as the only
argument against making them conditional is code size. But, these
being very small functions it shouldn't matter all that much.
I had left this open for discussion. Since I did not hear any
preferences, I will make these conditional as Arnd and I discussed.

No, this should not be combined with patch 5. The purpose of that
patch is not to include all the code that is conditional upon that
config.

-Deepa