[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABeXuvq5LyREPV1OqFvXb7HKXxQ9hQBh4G5oYTg-jchRwKa-EA@mail.gmail.com>
Date: Sun, 6 Nov 2016 13:14:05 -0800
From: Deepa Dinamani <deepa.kernel@...il.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Andreas Dilger <adilger@...ger.ca>,
"Theodore Ts'o" <tytso@....edu>,
Dave Chinner <david@...morbit.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Greg KH <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
y2038 Mailman List <y2038@...ts.linaro.org>,
linux-afs@...ts.infradead.org,
Andreas Dilger <adilger.kernel@...ger.ca>,
linux-ext4@...r.kernel.org
Subject: Re: [RFC 0/6] vfs: Add timestamp range check support
On Sun, Nov 6, 2016 at 12:28 PM, Arnd Bergmann <arnd@...db.de> wrote:
> On Sunday, November 6, 2016 9:44:33 AM CET Deepa Dinamani wrote:
>> I will post xfs tests that validate mount and range checking.
>> I will keep the policy same as what the RFC suggests for now.
>>
>> Clamping can be verified once vfs is transitioned to using time64_t.
>
> Won't it already work as expected on 64-bit architectures as they
> have a 64-bit time_t?
Yes, on 64 bit architectures, it should work fine.
32 bit machines will have wrong clamped timestamps though for some filesystems.
I can post a test for clamping that only works on 64 bit machines.
Thanks,
-Deepa
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists