From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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>
Subject: Re: [PATCH 3/3] fs/sysv: stop using write_super and s_dirt
Date: Tue, 3 Jul 2012 15:13:13 +0100 [thread overview]
Message-ID: <20120703151313.36e85254@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1341323008-29414-4-git-send-email-dedekind1@gmail.com>
> drity and then setting the s_dirt flag. And when 'write_super()' is executed to
> handle the s_dirt flag, we just update the timestamp and again mark the
> superblock buffer as dirty. Seems pointless.
It's the way sysv itself does stuff. The timestamp on v7/sys3/sys5
reflects the clock on the box. A lot of ancient boxes with no decent
hardware clocks used to reset the system time off the root fs superblock
on a loss of power.
Alan
next prev parent reply other threads:[~2012-07-03 14:09 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 " 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 [this message]
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
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=20120703151313.36e85254@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dedekind1@gmail.com \
--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
all inboxes | Powered by JetHome®