From: Chris Mason <chris.mason@fusionio.com>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"mitch.harder@sabayonlinux.org" <mitch.harder@sabayonlinux.org>,
"dsterba@suse.cz" <dsterba@suse.cz>
Subject: Re: [PATCH v2] Btrfs: fix race between snapshot deletion and getting inode
Date: Mon, 28 Jan 2013 22:52:16 -0500 [thread overview]
Message-ID: <20130129035216.GC23893@shiny.globalsuite.net> (raw)
In-Reply-To: <1359429730-16729-1-git-send-email-bo.li.liu@oracle.com>
On Mon, Jan 28, 2013 at 08:22:10PM -0700, Liu Bo wrote:
> While running snapshot testscript created by Mitch and David,
> the race between autodefrag and snapshot deletion can lead to
> corruption of dead_root list so that we can get crash on
> btrfs_clean_old_snapshots().
Really nice. Thanks to everyone that hashed this out.
-chris
next prev parent reply other threads:[~2013-01-29 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 3:22 [PATCH v2] Btrfs: fix race between snapshot deletion and getting inode Liu Bo
2013-01-29 3:52 ` Chris Mason [this message]
2013-01-30 15:09 ` Mitch Harder
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=20130129035216.GC23893@shiny.globalsuite.net \
--to=chris.mason@fusionio.com \
--cc=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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).