From: Jan Kara <jack@suse.cz>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH 6/6] ext3: Fix fsync error handling after filesystem abort.
Date: Tue, 28 May 2013 23:33:57 +0200 [thread overview]
Message-ID: <20130528213357.GD16408@quack.suse.cz> (raw)
In-Reply-To: <1369732741-26070-7-git-send-email-dmonakhov@openvz.org>
On Tue 28-05-13 13:19:01, Dmitry Monakhov wrote:
> If filesystem was aborted we will return success
> due to (sb->s_flags & MS_RDONLY) which is incorrect and
> 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
> - fix smp_rmb()/debug order
I've taken this patch to my tree with some minor spelling fixes.
Honza
>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
> ---
> fs/ext3/fsync.c | 8 ++++++--
> fs/ext3/super.c | 13 ++++++++++++-
> 2 files changed, 18 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ext3/fsync.c b/fs/ext3/fsync.c
> index b31dbd4..5412916 100644
> --- a/fs/ext3/fsync.c
> +++ b/fs/ext3/fsync.c
> @@ -48,9 +48,13 @@ int ext3_sync_file(struct file *file, loff_t start, loff_t end, int datasync)
>
> trace_ext3_sync_file_enter(file, datasync);
>
> - if (inode->i_sb->s_flags & MS_RDONLY)
> + if (inode->i_sb->s_flags & MS_RDONLY) {
> + /* Make shure that we read updated state */
> + smp_rmb();
> + if (EXT3_SB(inode->i_sb)->s_mount_state & EXT3_ERROR_FS)
> + return -EROFS;
> return 0;
> -
> + }
> ret = filemap_write_and_wait_range(inode->i_mapping, start, end);
> if (ret)
> goto out;
> diff --git a/fs/ext3/super.c b/fs/ext3/super.c
> index c8a4e17..b788bae 100644
> --- a/fs/ext3/super.c
> +++ b/fs/ext3/super.c
> @@ -174,6 +174,11 @@ static void ext3_handle_error(struct super_block *sb)
> if (test_opt (sb, ERRORS_RO)) {
> ext3_msg(sb, KERN_CRIT,
> "error: remounting filesystem read-only");
> + /*
> + * Make shure updated value of ->s_mount_state will be visiable
> + * before ->s_flags update.
> + */
> + smp_wmb();
> sb->s_flags |= MS_RDONLY;
> }
> ext3_commit_super(sb, es, 1);
> @@ -291,8 +296,14 @@ void ext3_abort(struct super_block *sb, const char *function,
> ext3_msg(sb, KERN_CRIT,
> "error: remounting filesystem read-only");
> EXT3_SB(sb)->s_mount_state |= EXT3_ERROR_FS;
> - sb->s_flags |= MS_RDONLY;
> set_opt(EXT3_SB(sb)->s_mount_opt, ABORT);
> + /*
> + * Make shure updated value of ->s_mount_state will be visiable
> + * before ->s_flags update.
> + */
> + smp_wmb();
> + sb->s_flags |= MS_RDONLY;
> +
> if (EXT3_SB(sb)->s_journal)
> journal_abort(EXT3_SB(sb)->s_journal, -EIO);
> }
> --
> 1.7.1
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2013-05-28 21:33 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
2013-05-28 9:19 ` [PATCH 6/6] ext3: " Dmitry Monakhov
2013-05-28 21:33 ` Jan Kara [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=20130528213357.GD16408@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).