linux-kernel - Re: [PATCH v4 1/5] vfs: Add file timestamp range support

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:   Sat, 25 Feb 2017 10:56:31 -0800
From:   Deepa Dinamani <deepa.kernel@...il.com>
To:     "Darrick J. Wong" <darrick.wong@...cle.com>
Cc:     Alexander Viro <viro@...iv.linux.org.uk>,
        "Theodore Ts'o" <tytso@....edu>,
        Andreas Dilger <adilger.kernel@...ger.ca>,
        linux-ext4@...r.kernel.org,
        Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>,
        y2038 Mailman List <y2038@...ts.linaro.org>
Subject: Re: [PATCH v4 1/5] vfs: Add file timestamp range support

> Just out of curiosity, does this enable 64-bit timestamps for everything
> by default?  I see that ext4 later sets its own values in fill_super;
> what about things like XFS that really only have 32-bit seconds fields?

This is just initializing limits for each filesystem.
Filesystems then override these limits with the actual limits they support.
This is what ext4 patch in the series is doing.
As the cover letter says, I will be submitting patches for all
filesystems to update limits.

This is no different than what is happening right now.
Right now, on 64 bit systems, VFS assumes timestamps to be 64 bits
long for all filesystems.

On 32 bit systems, the series only effects handling of dates beyond
the year 2038.
This is until vfs is transitioned to support 64 bit times. At which
point, the behavior on these will also be similar to 64 bit machines.

-Deepa