linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs corruption fix
Date: Fri, 17 Oct 2014 06:09:28 -0400	[thread overview]
Message-ID: <5440EAD8.4060801@fb.com> (raw)
In-Reply-To: <543F78F1.6040203@fb.com>



On 10/16/2014 03:51 AM, Chris Mason wrote:
> Hi Linus,
> 
> I'm testing a pull with more fixes, but wanted to get this one out so
> Greg can pick it up.  The corruption isn't easy to hit, you have to do a
> readonly snapshot and have orphans in the snapshot.  But my review and
> testing missed the bug.  Filipe has added a better xfstest to cover it.
> 
> Please pull:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus

Sorry Linus, I realized this morning I forgot my sob.  I've pushed out an
updated commit to a new for-linus-update branch.  The code and diffstat are 
exactly the same:

git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-update

> 
> Chris Mason (1) commits (+33/-36):
>     Revert "Btrfs: race free update of commit root for ro snapshots"
> 
> Total: (1) commits (+33/-36)
> 
>  fs/btrfs/inode.c | 36 ------------------------------------
>  fs/btrfs/ioctl.c | 33 +++++++++++++++++++++++++++++++++
>  2 files changed, 33 insertions(+), 36 deletions(-)
> 

-chris

      reply	other threads:[~2014-10-17 10:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16  7:51 [GIT PULL] Btrfs corruption fix Chris Mason
2014-10-17 10:09 ` Chris Mason [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=5440EAD8.4060801@fb.com \
    --to=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).