linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 3/4] vfs: Make __fsync_super() a static function (version 3)
Date: Thu, 23 Apr 2009 23:52:25 +0200	[thread overview]
Message-ID: <20090423215225.GD31584@duck.suse.cz> (raw)
In-Reply-To: <1240522790.8583.0.camel@heimdal.trondhjem.org>

On Thu 23-04-09 17:39:50, Trond Myklebust wrote:
> On Thu, 2009-04-23 at 23:35 +0200, Jan Kara wrote:
> > __fsync_super() does the same thing as fsync_super(). So change the only
> > caller to use fsync_super() and make __fsync_super() static. This removes
> > unnecessarily duplicated call to sync_blockdev() and prepares ground
> > for the changes to __fsync_super() in the following patches.
> > 
> > Signed-off-by: Jan Kara <jack@suse.cz>
> > ---
> >  fs/block_dev.c     |    2 +-
> >  fs/super.c         |    5 ++---
> >  include/linux/fs.h |    1 -
> >  3 files changed, 3 insertions(+), 5 deletions(-)
> > 
> > diff --git a/fs/block_dev.c b/fs/block_dev.c
> > index f45dbc1..48d1290 100644
> > --- a/fs/block_dev.c
> > +++ b/fs/block_dev.c
> > @@ -240,7 +240,7 @@ struct super_block *freeze_bdev(struct block_device *bdev)
> >  		sb->s_frozen = SB_FREEZE_WRITE;
> >  		smp_wmb();
> >  
> > -		__fsync_super(sb);
> > +		fsync_super(sb);
> >  
> >  		sb->s_frozen = SB_FREEZE_TRANS;
> >  		smp_wmb();
> > diff --git a/fs/super.c b/fs/super.c
> > index d9759e0..4c92068 100644
> > --- a/fs/super.c
> > +++ b/fs/super.c
> > @@ -263,7 +263,7 @@ EXPORT_SYMBOL(unlock_super);
> >   * device.  Takes the superblock lock.  Requires a second blkdev
> >   * flush by the caller to complete the operation.
> >   */
> > -void __fsync_super(struct super_block *sb)
> > +static int __fsync_super(struct super_block *sb)
> >  {
> >  	sync_inodes_sb(sb, 0);
> >  	vfs_dq_sync(sb);
> 
> Still missing the return value here :-)
  Ah, OK, but it's fixed in the last patch. I'll fix it in this one as well
for next time. Thanks.

									Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2009-04-23 21:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 21:35 [PATCH 0/4] Fix sys_sync() and cleanup code (version 3) Jan Kara
2009-04-23 21:35 ` [PATCH 1/4] vfs: Fix sys_sync() and fsync_super() reliability " Jan Kara
2009-04-23 21:35 ` [PATCH 2/4] vfs: Call ->sync_fs() even if s_dirt is 0 " Jan Kara
2009-04-23 21:35 ` [PATCH 3/4] vfs: Make __fsync_super() a static function " Jan Kara
2009-04-23 21:39   ` Trond Myklebust
2009-04-23 21:52     ` Jan Kara [this message]
2009-04-23 21:35 ` [PATCH 4/4] vfs: Make sys_sync() use fsync_super() " Jan Kara
2009-04-24 18:13 ` [PATCH 0/4] Fix sys_sync() and cleanup code " Christoph Hellwig
2009-04-26 11:54 ` Christoph Hellwig
2009-04-27 13:27   ` 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=20090423215225.GD31584@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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).