linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Yunlei He <heyunlei@huawei.com>,
	linux-f2fs-devel@lists.sourceforge.net, yuchao0@huawei.com,
	jaegeuk@kernel.org
Subject: Re: [PATCH] fsck: introduce generic function f2fs_fsync_device
Date: Tue, 17 Oct 2017 21:35:51 +0800	[thread overview]
Message-ID: <0d031dd4-d2ef-a668-d41e-1c1df022d852@kernel.org> (raw)
In-Reply-To: <1508223831-29251-1-git-send-email-heyunlei@huawei.com>

On 2017/10/17 15:03, Yunlei He wrote:
> We use f2fs_finalize_device to fsync previous data in
> checkpoint area before write last CP pack, in order to avoid
> cp corruption in sudden-power-off case. But this function will
> close the device, so this patch introduce a function to call
> fsync() only.
> 
> Signed-off-by: Yunlei He <heyunlei@huawei.com>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

> ---
>  fsck/mount.c      |  2 +-
>  include/f2fs_fs.h |  1 +
>  lib/libf2fs_io.c  | 10 ++++++++++
>  3 files changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/fsck/mount.c b/fsck/mount.c
> index 7a8aeae..e234fe9 100644
> --- a/fsck/mount.c
> +++ b/fsck/mount.c
> @@ -1939,7 +1939,7 @@ void write_checkpoint(struct f2fs_sb_info *sbi)
>  		write_nat_bits(sbi, sb, cp, sbi->cur_cp);
>  
>  	/* in case of sudden power off */
> -	f2fs_finalize_device();
> +	f2fs_fsync_device();
>  
>  	/* write the last cp */
>  	ret = dev_write_block(cp, cp_blk_no++);
> diff --git a/include/f2fs_fs.h b/include/f2fs_fs.h
> index bd609b9..3673817 100644
> --- a/include/f2fs_fs.h
> +++ b/include/f2fs_fs.h
> @@ -1013,6 +1013,7 @@ extern int f2fs_dev_is_umounted(char *);
>  extern int f2fs_get_device_info(void);
>  extern int get_device_info(int);
>  extern void f2fs_finalize_device(void);
> +extern void f2fs_fsync_device(void);
>  
>  extern int dev_read(void *, __u64, size_t);
>  extern int dev_write(void *, __u64, size_t);
> diff --git a/lib/libf2fs_io.c b/lib/libf2fs_io.c
> index aa99068..50ff171 100644
> --- a/lib/libf2fs_io.c
> +++ b/lib/libf2fs_io.c
> @@ -193,6 +193,16 @@ int dev_reada_block(__u64 blk_addr)
>  	return dev_readahead(blk_addr << F2FS_BLKSIZE_BITS, F2FS_BLKSIZE);
>  }
>  
> +void f2fs_fsync_device(void)
> +{
> +	int i;
> +
> +	for (i = 0; i < c.ndevs; i++) {
> +		if (fsync(c.devices[i].fd) < 0)
> +			MSG(0, "\tError: Could not conduct fsync!!!\n");
> +	}
> +}
> +
>  void f2fs_finalize_device(void)
>  {
>  	int i;
> 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

      reply	other threads:[~2017-10-17 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17  7:03 [PATCH] fsck: introduce generic function f2fs_fsync_device Yunlei He
2017-10-17 13:35 ` Chao Yu [this message]

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=0d031dd4-d2ef-a668-d41e-1c1df022d852@kernel.org \
    --to=chao@kernel.org \
    --cc=heyunlei@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=yuchao0@huawei.com \
    /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).