From: Joel Becker <Joel.Becker@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jan Kara <jack@suse.cz>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 4/5] ocfs2: remove ->write_super and stop maintaining ->s_dirt
Date: Tue, 28 Apr 2009 09:45:28 -0700 [thread overview]
Message-ID: <20090428164528.GA25290@mail.oracle.com> (raw)
In-Reply-To: <20090427134815.960338000@bombadil.infradead.org>
On Mon, Apr 27, 2009 at 09:46:44AM -0400, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Joel Becker <joel.becker@oracle.com>
>
> Index: linux-2.6/fs/ocfs2/super.c
> ===================================================================
> --- linux-2.6.orig/fs/ocfs2/super.c 2009-04-26 20:17:12.088104363 +0200
> +++ linux-2.6/fs/ocfs2/super.c 2009-04-26 20:17:22.988951278 +0200
> @@ -126,7 +126,6 @@ static int ocfs2_get_sector(struct super
> struct buffer_head **bh,
> int block,
> int sect_size);
> -static void ocfs2_write_super(struct super_block *sb);
> static struct inode *ocfs2_alloc_inode(struct super_block *sb);
> static void ocfs2_destroy_inode(struct inode *inode);
> static int ocfs2_susp_quotas(struct ocfs2_super *osb, int unsuspend);
> @@ -141,7 +140,6 @@ static const struct super_operations ocf
> .clear_inode = ocfs2_clear_inode,
> .delete_inode = ocfs2_delete_inode,
> .sync_fs = ocfs2_sync_fs,
> - .write_super = ocfs2_write_super,
> .put_super = ocfs2_put_super,
> .remount_fs = ocfs2_remount,
> .show_options = ocfs2_show_options,
> @@ -365,24 +363,12 @@ static struct file_operations ocfs2_osb_
> .llseek = generic_file_llseek,
> };
>
> -/*
> - * write_super and sync_fs ripped right out of ext3.
> - */
> -static void ocfs2_write_super(struct super_block *sb)
> -{
> - if (mutex_trylock(&sb->s_lock) != 0)
> - BUG();
> - sb->s_dirt = 0;
> -}
> -
> static int ocfs2_sync_fs(struct super_block *sb, int wait)
> {
> int status;
> tid_t target;
> struct ocfs2_super *osb = OCFS2_SB(sb);
>
> - sb->s_dirt = 0;
> -
> if (ocfs2_is_hard_readonly(osb))
> return -EROFS;
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
"The cynics are right nine times out of ten."
- H. L. Mencken
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2009-04-28 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 13:46 [PATCH 0/5] remove superflous ->write_super instances Christoph Hellwig
2009-04-27 13:46 ` [PATCH 1/5] btrfs: remove ->write_super and stop maintaining ->s_dirt Christoph Hellwig
2009-04-27 13:46 ` [PATCH 2/5] ext3: " Christoph Hellwig
2009-04-27 13:46 ` [PATCH 3/5] gfs2: " Christoph Hellwig
2009-04-27 15:49 ` Steven Whitehouse
2009-04-27 13:46 ` [PATCH 4/5] ocfs2: " Christoph Hellwig
2009-04-28 16:45 ` Joel Becker [this message]
2009-04-27 13:46 ` [PATCH 5/5] qnx4: remove ->write_super Christoph Hellwig
2009-04-27 14:32 ` [PATCH 0/5] remove superflous ->write_super instances Theodore Tso
2009-04-27 14:36 ` Christoph Hellwig
2009-04-27 16:54 ` Theodore Tso
2009-04-27 14:55 ` Jan Kara
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=20090428164528.GA25290@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).