From: Arnd Bergmann <arnd@arndb.de>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, y2038@lists.linaro.org,
tglx@linutronix.de, viro@zeniv.linux.org.uk
Subject: Re: [PATCH RESEND] vfs: Add support to document max and min inode times
Date: Sat, 9 Apr 2016 03:18:35 +0200 [thread overview]
Message-ID: <201604090318.35897.arnd@arndb.de> (raw)
In-Reply-To: <1460130933-8307-1-git-send-email-deepa.kernel@gmail.com>
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 <deepa.kernel@gmail.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2016-04-09 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 15:55 [PATCH RESEND] vfs: Add support to document max and min inode times Deepa Dinamani
2016-04-09 1:18 ` Arnd Bergmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201604090318.35897.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.