From: Andrew Morton <akpm@digeo.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Chris Mason <mason@suse.com>,
"Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: [PATCH] 2.5.x write_super is not for syncing
Date: Tue, 03 Dec 2002 14:13:15 -0800 [thread overview]
Message-ID: <3DED2C7B.135E8F0D@digeo.com> (raw)
In-Reply-To: OF451DCC33.99B3FAB9-ON87256C84.00765988-88256C84.00771BAD@boulder.ibm.com
Bryan Henderson wrote:
>
> >The intent is that ->sync_fs() should only be
> >called for sync, unmount, etc.
>
> Why unmount, etc.? That's just more assumption-making by FS as to what
> these operations require for every filesystem type.
>
> unmount, which in general requires a rather different kind of syncing than
> sync(), already has its own VFS call.
> I don't know what etc. would be but it's probably also something a
> filesystem driver might want to distinguish from sync().
Well, I'd say that telling the fs about umount activity is "out
of scope" for this exercise ;)
It seems reasonable to have a super_op which says "sync everything
to disk". And to call that in response to /bin/sync and unmount.
Doesn't it?
next prev parent reply other threads:[~2002-12-03 22:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1034791206.18503.68.camel@tiny>
2002-12-02 22:07 ` [PATCH] 2.5.x write_super is not for syncing Andrew Morton
2002-12-02 23:40 ` Chris Mason
2002-12-03 0:03 ` Andrew Morton
2002-12-03 1:10 ` Chris Mason
2002-12-03 1:40 ` Andrew Morton
2002-12-03 3:09 ` Andrew Morton
2002-12-03 19:36 ` Bryan Henderson
2002-12-03 20:06 ` Andrew Morton
2002-12-03 21:41 ` Bryan Henderson
2002-12-03 22:13 ` Andrew Morton [this message]
2002-12-04 2:05 ` Bryan Henderson
2002-12-04 4:29 ` Andrew Morton
2002-12-04 19:00 ` Bryan Henderson
2002-12-04 19:23 ` Matthew Wilcox
2002-12-04 22:17 ` Bryan Henderson
2002-12-05 10:36 ` Arnaldo Carvalho de Melo
2002-12-05 16:31 ` Stephen C. Tweedie
2002-12-05 17:24 ` girish
2002-12-04 21:10 ` Stephen C. Tweedie
2002-12-04 22:46 ` Bryan Henderson
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=3DED2C7B.135E8F0D@digeo.com \
--to=akpm@digeo.com \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mason@suse.com \
--cc=sct@redhat.com \
/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