From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([212.227.17.13]:49169 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752097AbcDIBSs (ORCPT ); Fri, 8 Apr 2016 21:18:48 -0400 From: Arnd Bergmann To: Deepa Dinamani Subject: Re: [PATCH RESEND] vfs: Add support to document max and min inode times Date: Sat, 9 Apr 2016 03:18:35 +0200 Cc: linux-fsdevel@vger.kernel.org, y2038@lists.linaro.org, tglx@linutronix.de, viro@zeniv.linux.org.uk References: <1460130933-8307-1-git-send-email-deepa.kernel@gmail.com> In-Reply-To: <1460130933-8307-1-git-send-email-deepa.kernel@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201604090318.35897.arnd@arndb.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Friday 08 April 2016, Deepa Dinamani wrote: > This is a preparation patch to add range checking for inode > timestamps. > > Extend struct super_block to include information about the max > and min inode times each filesystem can hold. These are dependent > on the on-disk format of filesystems. > > These range checks will be used to clamp timestamps to filesystem > allowed ranges. > > Individual filesystems do not have the same on disk format as > the in memory inodes. Range checking and clamping times assigned > to inodes will help keep in memory and on-disk timestamps to be > in sync. > > Another series will initialize these fields to appropriate values for > every filesystem. > > The fields are not used by vfs yet. > The exact policy and behavior will be decided in a separate patch. > > The original idea for the feature comes from the discussion: > https://lkml.org/lkml/2014/5/30/669 > > Signed-off-by: Deepa Dinamani Reviewed-by: Arnd Bergmann