From: Sage Weil <sage@newdream.net>
To: Chris Mason <chris.mason@oracle.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fix sync subvol/snapshot creation
Date: Thu, 9 Dec 2010 18:20:44 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.1012091818000.29614@cobra.newdream.net> (raw)
In-Reply-To: <1291947062-sup-3515@think>
On Thu, 9 Dec 2010, Chris Mason wrote:
> Excerpts from Li Zefan's message of 2010-12-09 21:11:25 -0500:
> > Sage Weil wrote:
> > > We were incorrectly taking the async path even for the sync ioctls by
> > > passing in &transid unconditionally.
> > >
> >
> > Ha, I fixed this accidentally in my patchset. :)
>
> Thanks guys,
>
> Unless either of you object, I'll take this and the snapshot ABI change
> for the next rc.
Sounds good to me.
Just FYI, I'm still seeing some weird corruption and crashes on my
machines and haven't narrowed it down yet. Should have more info soon.
sage
prev parent reply other threads:[~2010-12-10 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 0:36 [PATCH] Btrfs: fix sync subvol/snapshot creation Sage Weil
2010-12-10 2:11 ` Li Zefan
2010-12-10 2:11 ` Chris Mason
2010-12-10 2:20 ` Sage Weil [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=Pine.LNX.4.64.1012091818000.29614@cobra.newdream.net \
--to=sage@newdream.net \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
/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).