From: Boaz Harrosh <bharrosh@panasas.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
Benny Halevy <bhalevy@tonian.com>, <osd-dev@open-osd.org>
Subject: Re: [PATCH] exofs: stop using s_dirt
Date: Mon, 4 Jun 2012 19:12:54 +0300 [thread overview]
Message-ID: <4FCCDE86.4060507@panasas.com> (raw)
In-Reply-To: <1338810507-26539-1-git-send-email-dedekind1@gmail.com>
On 06/04/2012 02:48 PM, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
>
> Exofs has the '->write_super()' handler and makes some use of the '->s_dirt'
> superblock flag, but it really needs neither of them because it never sets
> 's_dirt' to one which means the VFS never calls its '->write_super()' handler.
> Thus, remove both.
>
Thanks Artem. I have seen your other FS conversions and thought I would
eventually need to also do it for exofs, thanks for beating me to it ;-)
I have removed all uses of sb->s_dirt = 1 cases around last year, by
writing the SB-info as part of the create/delete commands directly. So
I agree it is not needed anymore see here
1cea312 exofs: Write sbi->s_nextid as part of the Create command
I have one question though, which I did not understand at the time?
Today at exofs_write_super() we call exofs_sync_fs() (super_operations->sync_fs)
Who/when calls ->sync_fs() without the ->write_super() below.
But otherwise I agree that sb->s_dirt = 1 and ->write_super() are not needed
at all, for regular operations.
Should I take this for 3.6 through my tree. Or do you want my:
Ack-by: Boaz Harrosh <bharrosh@panasas.com>
> Note, I am trying to remove both 's_dirt' and 'write_super()' from VFS
> altogether once all users are gone.
>
> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> ---
> fs/exofs/super.c | 11 -----------
> 1 files changed, 0 insertions(+), 11 deletions(-)
>
> diff --git a/fs/exofs/super.c b/fs/exofs/super.c
> index 735ca06..6e1c515 100644
> --- a/fs/exofs/super.c
> +++ b/fs/exofs/super.c
> @@ -400,8 +400,6 @@ static int exofs_sync_fs(struct super_block *sb, int wait)
> ret = ore_write(ios);
> if (unlikely(ret))
> EXOFS_ERR("%s: ore_write failed.\n", __func__);
> - else
> - sb->s_dirt = 0;
>
>
> unlock_super(sb);
> @@ -412,14 +410,6 @@ out:
> return ret;
> }
>
> -static void exofs_write_super(struct super_block *sb)
> -{
> - if (!(sb->s_flags & MS_RDONLY))
> - exofs_sync_fs(sb, 1);
> - else
> - sb->s_dirt = 0;
> -}
> -
> static void _exofs_print_device(const char *msg, const char *dev_path,
> struct osd_dev *od, u64 pid)
> {
> @@ -942,7 +932,6 @@ static const struct super_operations exofs_sops = {
> .write_inode = exofs_write_inode,
> .evict_inode = exofs_evict_inode,
> .put_super = exofs_put_super,
> - .write_super = exofs_write_super,
> .sync_fs = exofs_sync_fs,
> .statfs = exofs_statfs,
> };
next prev parent reply other threads:[~2012-06-04 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 11:48 [PATCH] exofs: stop using s_dirt Artem Bityutskiy
2012-06-04 16:12 ` Boaz Harrosh [this message]
2012-06-05 7:35 ` Artem Bityutskiy
2012-06-05 10:35 ` Artem Bityutskiy
2012-06-05 13:02 ` Boaz Harrosh
2012-06-21 12:29 ` Artem Bityutskiy
2012-06-27 15:49 ` Boaz Harrosh
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=4FCCDE86.4060507@panasas.com \
--to=bharrosh@panasas.com \
--cc=bhalevy@tonian.com \
--cc=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osd-dev@open-osd.org \
/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