From: Theodore Ts'o <tytso@mit.edu>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: jfs-discussion@lists.sourceforge.net, Jan Kara <jack@suse.cz>,
Anders Larsen <al@alarsen.net>,
linux-mtd@lists.infradead.org,
Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>,
Petr Vandrovec <petr@vandrovec.name>,
linux-cifs@vger.kernel.org, linux-fsdevel@thunk.org,
cluster-devel@redhat.com,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Evgeniy Dushistov <dushistov@mail.ru>,
Kees Cook <keescook@chromium.org>,
fuse-devel@lists.sourceforge.net, reiserfs-devel@vger.kernel.org,
xfs@oss.sgi.com, linux-nilfs@vger.kernel.org,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
codalist@TELEMANN.coda.cs.cmu.edu, linux-nfs@vger.kernel.org,
Artem Bityutskiy <dedekind1@gmail.com>,
linux-ntfs-dev@lists.sourceforge.net,
samba-technical@lists.samba.org,
Adrian Hunter <adrian.hunter@intel.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.k
Subject: Re: [Cluster-devel] [PATCH] fs: push sync_filesystem() down to the file system's remount_fs()
Date: Thu, 13 Mar 2014 19:15:06 -0400 [thread overview]
Message-ID: <20140313231506.GB16785@thunk.org> (raw)
In-Reply-To: <1394728103.2767.32.camel@menhir>
On Thu, Mar 13, 2014 at 04:28:23PM +0000, Steven Whitehouse wrote:
>
> I guess the same is true for other file systems which are mounted ro
> too. So maybe a check for MS_RDONLY before doing the sync in those
> cases?
My original patch moved the sync_filesystem into the check for
MS_RDONLY in the core VFS code. The objection was raised that there
might be some file system out there that might depend on this
behaviour. I can't imagine why, but I suppose it's at least
theoretically possible.
So the idea is that this particular patch is *guaranteed* not to make
any difference. That way there can be no question about the patch'es
correctness.
I'm going to follow up with a patch for ext4 that does exactly that,
but the idea is to allow each file system maintainer to do that for
their own file system.
I could do that as well for file systems that are "obviously"
read-only, but then I'll find out that there's some wierd case where
the file system can be used in a read-write fashion. (Example: UDF is
normally used for DVD's, but at least in theory it can be used
read/write --- I'm told that Windows supports read-write UDF file
systems on USB sticks, and at least in theory it could be used as a
inter-OS exchange format in situations where VFAT and exFAT might not
be appropriate for various reasons.)
Cheers,
- Ted
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
next prev parent reply other threads:[~2014-03-13 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140313073936.GA14663@infradead.org>
2014-03-13 14:20 ` [PATCH] fs: push sync_filesystem() down to the file system's remount_fs() Theodore Ts'o
2014-03-13 14:50 ` Anders Larsen
[not found] ` <1394720456-16629-1-git-send-email-tytso-3s7WtUTddSA@public.gmane.org>
2014-03-13 16:23 ` Jan Kara
2014-03-13 16:28 ` Steven Whitehouse
2014-03-13 23:15 ` Theodore Ts'o [this message]
[not found] ` <20140313231506.GB16785-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2014-03-14 12:13 ` [Cluster-devel] " Jan Kara
2014-03-14 0:33 ` Steve French
2014-03-14 1:23 ` Theodore Ts'o
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=20140313231506.GB16785@thunk.org \
--to=tytso@mit.edu \
--cc=adrian.hunter@intel.com \
--cc=al@alarsen.net \
--cc=cluster-devel@redhat.com \
--cc=codalist@TELEMANN.coda.cs.cmu.edu \
--cc=dedekind1@gmail.com \
--cc=dushistov@mail.ru \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=keescook@chromium.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@thunk.org \
--cc=linux-fsdevel@vger.k \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=petr@vandrovec.name \
--cc=reiserfs-devel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=swhiteho@redhat.com \
--cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).