From: Boaz Harrosh <bharrosh@panasas.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@ZenIV.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] remove ->write_super call in generic_shutdown_super
Date: Thu, 30 Apr 2009 11:35:26 +0300 [thread overview]
Message-ID: <49F962CE.8010907@panasas.com> (raw)
In-Reply-To: <20090428160026.GB26363@lst.de>
On 04/28/2009 07:00 PM, Christoph Hellwig wrote:
> We just did a full fs writeout using sync_filesystem before, and if
> that's not enough for the filesystem it can perform it's own writeout
> in ->put_super, which many filesystems already do.
>
> Move a call to foofs_write_super into every foofs_put_super for now to
> guarantee identical behaviour until it's cleaned up by the individual
> filesystem maintainers.
>
> Exceptions:
>
> - affs already has identical copy & pasted code at the beginning of
> affs_put_super so no need to do it twice.
> - xfs does the right thing without it and I have changes pending for
> the xfs tree touching this are so I don't really need conflicts
> here..
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
<snip>
> ===================================================================
> --- linux-2.6.orig/fs/exofs/super.c 2009-04-28 17:45:49.232482198 +0200
> +++ linux-2.6/fs/exofs/super.c 2009-04-28 17:47:50.303050752 +0200
> @@ -258,6 +258,9 @@ static void exofs_put_super(struct super
> int num_pend;
> struct exofs_sb_info *sbi = sb->s_fs_info;
>
> + if (sb->s_dirt)
> + exofs_write_super(sb);
> +
> /* make sure there are no pending commands */
> for (num_pend = atomic_read(&sbi->s_curr_pending); num_pend > 0;
> num_pend = atomic_read(&sbi->s_curr_pending)) {
Ack-by: Boaz Harrosh <bharrosh@panasas.com>
<snip>
I'll put it on my TODO list to see if this can be removed, later.
Boaz
next prev parent reply other threads:[~2009-04-30 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 16:00 [PATCH] remove ->write_super call in generic_shutdown_super Christoph Hellwig
2009-04-30 8:35 ` Boaz Harrosh [this message]
2009-05-02 2:51 ` Ryusuke Konishi
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=49F962CE.8010907@panasas.com \
--to=bharrosh@panasas.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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 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.