From: Filipe David Manana <fdmanana@gmail.com>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fix data loss of fsync
Date: Thu, 5 Mar 2015 09:59:09 +0000 [thread overview]
Message-ID: <CAL3q7H6mx573exkLZF-8yz2EpKucrd2KCgj6Chf_Jd8SH56PfQ@mail.gmail.com> (raw)
In-Reply-To: <1425545307-3721-1-git-send-email-bo.li.liu@oracle.com>
On Thu, Mar 5, 2015 at 8:48 AM, Liu Bo <bo.li.liu@oracle.com> wrote:
> This problem is uncovered by a test case: http://patchwork.ozlabs.org/patch/244297.
>
> Fsync() can report success when it actually doesn't. When we
> have several threads running fsync() at the same tiem and in one fsync() we
> get a transaction abortion due to some problems(in the test case it's disk
> failures), and other fsync()s may return successfully which makes userspace
> programs think that data is now safely flushed into disk.
>
> It's because that after fsyncs() fail btrfs_sync_log() due to disk failures,
> they get to try btrfs_commit_transaction() where it finds that there is
> already a transaction being committed, and they'll just call wait_for_commit()
> and return. Note that we actually check "trans->aborted" in btrfs_end_transaction,
> but it's likely that the error message is still not yet throwed out and only after
> wait_for_commit() we're sure whether the transaction is committed successfully.
>
> This add the necessary check and it now passes the test.
>
> Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
The change itself is ok but the title and associating it only with
fsync are not quite right, since this is much more generic and not
specific to fsync.
thanks
> ---
> fs/btrfs/transaction.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c
> index 7e80f32..bd7ea86 100644
> --- a/fs/btrfs/transaction.c
> +++ b/fs/btrfs/transaction.c
> @@ -1814,6 +1814,9 @@ int btrfs_commit_transaction(struct btrfs_trans_handle *trans,
>
> wait_for_commit(root, cur_trans);
>
> + if (unlikely(ACCESS_ONCE(cur_trans->aborted)))
> + ret = cur_trans->aborted;
> +
> btrfs_put_transaction(cur_trans);
>
> return ret;
> --
> 1.8.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
next prev parent reply other threads:[~2015-03-05 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 8:48 [PATCH] Btrfs: fix data loss of fsync Liu Bo
2015-03-05 9:59 ` Filipe David Manana [this message]
2015-03-05 10:23 ` Liu Bo
2015-03-05 10:28 ` Filipe David Manana
2015-03-05 10:36 ` [PATCH V2] Btrfs: catch transaction abortion after waiting for it Liu Bo
2015-03-05 13:59 ` Chris Mason
2015-03-06 11:42 ` Liu Bo
2015-03-06 12:23 ` [PATCH v3] " Liu Bo
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=CAL3q7H6mx573exkLZF-8yz2EpKucrd2KCgj6Chf_Jd8SH56PfQ@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@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).