From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([212.227.126.134]:64395 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751093AbcKFU3T (ORCPT ); Sun, 6 Nov 2016 15:29:19 -0500 From: Arnd Bergmann To: Deepa Dinamani Cc: Andreas Dilger , Theodore Ts'o , Dave Chinner , linux-fsdevel , LKML , Thomas Gleixner , Greg KH , Andrew Morton , Alexander Viro , y2038 Mailman List , linux-afs@lists.infradead.org, Andreas Dilger , linux-ext4@vger.kernel.org Subject: Re: [RFC 0/6] vfs: Add timestamp range check support Date: Sun, 06 Nov 2016 21:28:37 +0100 Message-ID: <147897712.8Iuj6e9dPp@wuerfel> In-Reply-To: References: <1478099096-25637-1-git-send-email-deepa.kernel@gmail.com> <1206C36E-9CB4-47B3-A891-8EA94C3220E0@dilger.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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? Arnd