linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	linux-fsdevel@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Curt Wohlgemuth <curtw@google.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes
Date: Tue, 17 Jul 2012 14:27:34 +0800	[thread overview]
Message-ID: <20120717062734.GA6698@localhost> (raw)
In-Reply-To: <1341326734-29881-7-git-send-email-jack@suse.cz>

Hi Jan,

I got this error for !CONFIG_BLOCK builds:

fs/sync.c:110:2: error: implicit declaration of function 'iterate_bdevs' [-Werror=implicit-function-declaration]

Thanks,
Fengguang

On Tue, Jul 03, 2012 at 04:45:32PM +0200, Jan Kara wrote:
> In case block device does not have filesystem mounted on it, sys_sync will just
> ignore it and doesn't writeout its dirty pages. This is because writeback code
> avoids writing inodes from superblock without backing device and
> blockdev_superblock is such a superblock.  Since it's unexpected that sync
> doesn't writeout dirty data for block devices be nice to users and change the
> behavior to do so. So now we iterate over all block devices on blockdev_super
> instead of iterating over all superblocks when syncing block devices.
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
>  fs/sync.c |   18 +++++++++++-------
>  1 files changed, 11 insertions(+), 7 deletions(-)
> 
> diff --git a/fs/sync.c b/fs/sync.c
> index 867bf78..ea6e818 100644
> --- a/fs/sync.c
> +++ b/fs/sync.c
> @@ -85,10 +85,14 @@ static void sync_fs_one_sb(struct super_block *sb, void *arg)
>  		sb->s_op->sync_fs(sb, *(int *)arg);
>  }
>  
> -static void sync_blkdev_one_sb(struct super_block *sb, void *arg)
> +static void flush_one_bdev(struct block_device *bdev, void *arg)
>  {
> -	if (!(sb->s_flags & MS_RDONLY))
> -		__sync_blockdev(sb->s_bdev, *(int *)arg);
> +	__sync_blockdev(bdev, 0);
> +}
> +
> +static void sync_one_bdev(struct block_device *bdev, void *arg)
> +{
> +	sync_blockdev(bdev);
>  }
>  
>  /*
> @@ -102,10 +106,10 @@ SYSCALL_DEFINE0(sync)
>  	wakeup_flusher_threads(0, WB_REASON_SYNC);
>  	iterate_supers(writeback_inodes_one_sb, NULL);
>  	iterate_supers(sync_fs_one_sb, &nowait);
> -	iterate_supers(sync_blkdev_one_sb, &nowait);
> +	iterate_bdevs(flush_one_bdev, NULL);
>  	iterate_supers(sync_inodes_one_sb, NULL);
>  	iterate_supers(sync_fs_one_sb, &wait);
> -	iterate_supers(sync_blkdev_one_sb, &wait);
> +	iterate_bdevs(sync_one_bdev, NULL);
>  	if (unlikely(laptop_mode))
>  		laptop_sync_completion();
>  	return 0;
> @@ -121,10 +125,10 @@ static void do_sync_work(struct work_struct *work)
>  	 */
>  	iterate_supers(sync_inodes_one_sb, &nowait);
>  	iterate_supers(sync_fs_one_sb, &nowait);
> -	iterate_supers(sync_blkdev_one_sb, &nowait);
> +	iterate_bdevs(flush_one_bdev, NULL);
>  	iterate_supers(sync_inodes_one_sb, &nowait);
>  	iterate_supers(sync_fs_one_sb, &nowait);
> -	iterate_supers(sync_blkdev_one_sb, &nowait);
> +	iterate_bdevs(flush_one_bdev, NULL);
>  	printk("Emergency Sync complete\n");
>  	kfree(work);
>  }
> -- 
> 1.7.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2012-07-17  6:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 14:45 [PATCH 0/8 v4] Flush all block devices on sync(2) and cleanup the code Jan Kara
2012-07-03 14:45 ` [PATCH 1/8] vfs: Move noop_backing_dev_info check from sync into writeback Jan Kara
2012-07-03 14:45 ` [PATCH 2/8] quota: Split dquot_quota_sync() to writeback and cache flushing part Jan Kara
2012-07-03 14:45 ` [PATCH 3/8] quota: Move quota syncing to ->sync_fs method Jan Kara
2012-07-03 14:45 ` [PATCH 4/8] vfs: Reorder operations during sys_sync Jan Kara
2012-07-03 14:45 ` [PATCH 5/8] vfs: Create function for iterating over block devices Jan Kara
2012-07-03 14:45 ` [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes Jan Kara
2012-07-17  6:27   ` Fengguang Wu [this message]
2012-07-20  2:21     ` Fengguang Wu
2012-07-03 14:45 ` [PATCH 7/8] vfs: Remove unnecessary flushing of block devices Jan Kara
2012-07-03 14:45 ` [PATCH 8/8] vfs: Avoid unnecessary WB_SYNC_NONE writeback during sys_sync and reorder sync passes Jan Kara
  -- strict thread matches above, loose matches on Subject: below --
2012-01-05 23:46 [PATCH 0/8 RESEND] Cleanup and improve sync (v4) Jan Kara
2012-01-05 23:46 ` [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes Jan Kara
2012-06-20 14:23   ` Curt Wohlgemuth
2012-06-20 20:03     ` Jan Kara
2012-06-22 10:30       ` Al Viro
2012-07-03 14:47         ` Jan Kara
2011-11-09 17:44 [PATCH 0/8] Cleanup and improve sync (v4) Jan Kara
2011-11-09 17:45 ` [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes 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=20120717062734.GA6698@localhost \
    --to=fengguang.wu@intel.com \
    --cc=curtw@google.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 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).