From: Jan Kara <jack@suse.cz>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH 5/6] ext4: Fix fsync error handling after filesystem abort.
Date: Tue, 28 May 2013 23:29:22 +0200 [thread overview]
Message-ID: <20130528212922.GC16408@quack.suse.cz> (raw)
In-Reply-To: <1369732741-26070-6-git-send-email-dmonakhov@openvz.org>
On Tue 28-05-13 13:19:00, Dmitry Monakhov wrote:
> If filesystem was aborted after inode's write back is complete
> but before its metadata was updated we may return success
> results in data loss.
> In order to handle fs abort correctly we have to check
> fs state once we discover that it is in MS_RDONLY state
>
> Test case: http://patchwork.ozlabs.org/patch/244297
>
> Changes from V1:
> - fix spelling
Still not quite ;) Search for 'shure' and 'visiable'. But feel free to
add
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
> ---
> fs/ext4/fsync.c | 8 ++++++--
> fs/ext4/super.c | 12 +++++++++++-
> 2 files changed, 17 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ext4/fsync.c b/fs/ext4/fsync.c
> index e0ba8a4..d7df2f1 100644
> --- a/fs/ext4/fsync.c
> +++ b/fs/ext4/fsync.c
> @@ -129,9 +129,13 @@ int ext4_sync_file(struct file *file, loff_t start, loff_t end, int datasync)
> return ret;
> mutex_lock(&inode->i_mutex);
>
> - if (inode->i_sb->s_flags & MS_RDONLY)
> + if (inode->i_sb->s_flags & MS_RDONLY) {
> + /* Make shure that we read updated s_mount_flags value */
> + smp_rmb();
> + if (EXT4_SB(inode->i_sb)->s_mount_flags & EXT4_MF_FS_ABORTED)
> + ret = -EROFS;
> goto out;
> -
> + }
> ret = ext4_flush_unwritten_io(inode);
> if (ret < 0)
> goto out;
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index edc716d..b4154d3 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -399,6 +399,11 @@ static void ext4_handle_error(struct super_block *sb)
> }
> if (test_opt(sb, ERRORS_RO)) {
> ext4_msg(sb, KERN_CRIT, "Remounting filesystem read-only");
> + /*
> + * Make shure updated value of ->s_mount_flags will be visiable
> + * before ->s_flags update
> + */
> + smp_wmb();
> sb->s_flags |= MS_RDONLY;
> }
> if (test_opt(sb, ERRORS_PANIC))
> @@ -571,8 +576,13 @@ void __ext4_abort(struct super_block *sb, const char *function,
>
> if ((sb->s_flags & MS_RDONLY) == 0) {
> ext4_msg(sb, KERN_CRIT, "Remounting filesystem read-only");
> - sb->s_flags |= MS_RDONLY;
> EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
> + /*
> + * Make shure updated value of ->s_mount_flags will be visiable
> + * before ->s_flags update
> + */
> + smp_wmb();
> + sb->s_flags |= MS_RDONLY;
> if (EXT4_SB(sb)->s_journal)
> jbd2_journal_abort(EXT4_SB(sb)->s_journal, -EIO);
> save_error_info(sb, function, line);
> --
> 1.7.1
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-05-28 21:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 9:18 [PATCH 0/6] ext3/4 data integrity fixes Dmitry Monakhov
2013-05-28 9:18 ` [PATCH 1/6] jbd2: optimize jbd2_journal_force_commit Dmitry Monakhov
2013-05-28 21:22 ` Jan Kara
2013-06-03 11:16 ` Dmitry Monakhov
2013-06-10 13:07 ` Theodore Ts'o
2013-06-10 13:18 ` Dmitry Monakhov
2013-06-10 13:53 ` Theodore Ts'o
2013-05-28 9:18 ` [PATCH 2/6] ext4: fix data integrity for ext4_sync_fs Dmitry Monakhov
2013-05-28 21:51 ` Jan Kara
2013-06-03 11:30 ` Dmitry Monakhov
2013-05-28 9:18 ` [PATCH 3/6] jbd: optimize journal_force_commit Dmitry Monakhov
2013-05-28 9:18 ` [PATCH 4/6] ext3: fix data integrity for ext4_sync_fs Dmitry Monakhov
2013-05-28 21:40 ` Jan Kara
2013-05-28 9:19 ` [PATCH 5/6] ext4: Fix fsync error handling after filesystem abort Dmitry Monakhov
2013-05-28 21:29 ` Jan Kara [this message]
2013-05-28 9:19 ` [PATCH 6/6] ext3: " Dmitry Monakhov
2013-05-28 21:33 ` 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=20130528212922.GC16408@quack.suse.cz \
--to=jack@suse.cz \
--cc=dmonakhov@openvz.org \
--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;
as well as URLs for NNTP newsgroup(s).