From: Jan Kara <jack@suse.cz>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Ext4 Mailing List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext2: do not register write_super within VFS
Date: Wed, 4 Apr 2012 00:36:32 +0200 [thread overview]
Message-ID: <20120403223632.GA5288@quack.suse.cz> (raw)
In-Reply-To: <1333446558-28171-1-git-send-email-dedekind1@gmail.com>
On Tue 03-04-12 12:49:18, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
>
> Jan Kara removed 'sb->s_dirt' VFS flag references, so we do not need to
> register the ext2 'ext2_write_super()' method in the VFS superblock operations,
> because 'sb->s_dirt' won't be ever set to 1 and VFS won't ever call
> '->write_super()' anyway. Thus, remove the method.
>
> Tested using xfstests.
>
> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Thanks. Added to my tree.
Honza
> ---
> fs/ext2/super.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ext2/super.c b/fs/ext2/super.c
> index a43f9ad..e0e8f45 100644
> --- a/fs/ext2/super.c
> +++ b/fs/ext2/super.c
> @@ -302,7 +302,6 @@ static const struct super_operations ext2_sops = {
> .write_inode = ext2_write_inode,
> .evict_inode = ext2_evict_inode,
> .put_super = ext2_put_super,
> - .write_super = ext2_write_super,
> .sync_fs = ext2_sync_fs,
> .statfs = ext2_statfs,
> .remount_fs = ext2_remount,
> --
> 1.7.7.6
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2012-04-03 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 9:49 [PATCH] ext2: do not register write_super within VFS Artem Bityutskiy
2012-04-03 22:36 ` Jan Kara [this message]
2012-04-11 11:24 ` Artem Bityutskiy
2012-04-11 15:30 ` Jan Kara
2012-04-11 15:40 ` 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=20120403223632.GA5288@quack.suse.cz \
--to=jack@suse.cz \
--cc=dedekind1@gmail.com \
--cc=linux-ext4@vger.kernel.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