From: Artem Bityutskiy <dedekind1@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 0/3] fs/sysv: stop using write_supers and s_dirt
Date: Sat, 14 Jul 2012 07:04:29 +0300 [thread overview]
Message-ID: <1342238669.3209.4.camel@brekeke> (raw)
In-Reply-To: <20120713144244.f3c9fb27.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Fri, 2012-07-13 at 14:42 -0700, Andrew Morton wrote:
>
> The issue Alan raised around the superblock timestamp is still up in
> the air. I guess he's a slow typist ;)
>
> My take is "no, we don't need to do that any more" - surely all Linux
> systems have a functional hardware clock. But the changelog should be
> updated to describe and justify the decision.
>
While I do trust such system existed and may be even still exist, I
doubt that Linux sysv FS implementation is of any help for them because
it updates the superblock time-stamp _only_ if there was write activity,
otherwise it does not. So you cannot rely on our time-stamps at all
anyway. My patches just make it update the time-stamp more rarely.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-14 4:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 13:43 [PATCH 0/3] fs/sysv: stop using write_supers and s_dirt Artem Bityutskiy
2012-07-03 13:43 ` [PATCH 1/3] fs/sysv: remove useless write_super call Artem Bityutskiy
2012-07-03 13:43 ` [PATCH 2/3] fs/sysv: remove another " Artem Bityutskiy
2012-07-03 13:43 ` [PATCH 3/3] fs/sysv: stop using write_super and s_dirt Artem Bityutskiy
2012-07-03 14:13 ` Alan Cox
2012-07-03 14:44 ` Artem Bityutskiy
2012-07-12 14:37 ` [PATCH 0/3] fs/sysv: stop using write_supers " Artem Bityutskiy
2012-07-12 14:49 ` Artem Bityutskiy
2012-07-13 21:42 ` Andrew Morton
2012-07-14 4:04 ` Artem Bityutskiy [this message]
2012-07-17 15:13 ` Artem Bityutskiy
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=1342238669.3209.4.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).