From: Chris Mason <clm@fb.com>
To: Filipe Manana <fdmanana@gmail.com>
Cc: <linux-btrfs@vger.kernel.org>, <stable@vger.kernel.org>,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] Revert "Btrfs: race free update of commit root for ro snapshots"
Date: Wed, 15 Oct 2014 17:11:55 -0400 [thread overview]
Message-ID: <1413407515.18175.0@mail.thefacebook.com> (raw)
In-Reply-To: <1413398246-17324-1-git-send-email-fdmanana@suse.com>
On Wed, Oct 15, 2014 at 2:37 PM, Filipe Manana <fdmanana@gmail.com>
wrote:
> This reverts commit 9c3b306e1c9e6be4be09e99a8fe2227d1005effc.
>
> Switching only one commit root during a transaction is wrong because
> it leads
> the fs into an inconsistent state. All commit roots should be
> switched at once,
> at transaction commit time, otherwise backref walking can often miss
> important
> references that were only accessible through the old commit root.
> Plus, the root item for the snapshot's root wasn't getting updated
> and preventing
> the next transaction commit to do it.
>
> This made several users get into random corruption issues after
> creation of
> readonly snapshots.
Thanks Filipe and everyone else that helped nail this down. I
convinced myself that working on readonly roots made the original
commit ok, but clearly I was horribly wrong. Sorry guys, I'll get this
off to Linus as soon as I do a quick cook here.
-chris
next prev parent reply other threads:[~2014-10-15 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 18:37 [PATCH] Revert "Btrfs: race free update of commit root for ro snapshots" Filipe Manana
2014-10-15 21:11 ` Chris Mason [this message]
2014-10-15 22:42 ` john terragon
2014-10-15 23:05 ` Filipe David Manana
2014-10-15 23:49 ` john terragon
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=1413407515.18175.0@mail.thefacebook.com \
--to=clm@fb.com \
--cc=fdmanana@gmail.com \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@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).