From: Chris Samuel <chris@csamuel.org>
To: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Josef Bacik <josef@redhat.com>,
Chris Mason <chris.mason@oracle.com>,
stable@vger.kernel.org, linux-btrfs@vger.kernel.org,
ceph-devel@vger.kernel.org
Subject: Re: ceph-on-btrfs inline-cow regression fix for 3.4.3
Date: Wed, 13 Jun 2012 15:04:06 +1000 [thread overview]
Message-ID: <4FD81F46.3010702@csamuel.org> (raw)
In-Reply-To: <orvcivvppp.fsf@livre.localdomain>
On 13/06/12 13:46, Alexandre Oliva wrote:
> I know btrfs hasn't had maintenance fixes in stable series, but Chris
> Mason tells me the only reason is that nobody stepped up to do so.
> Given my interest, I might as well give it a try ;-)
Actually 3.3.3 had a fix for btrfs in it.. :-)
http://lwn.net/Articles/493971/
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
next prev parent reply other threads:[~2012-06-13 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 3:46 ceph-on-btrfs inline-cow regression fix for 3.4.3 Alexandre Oliva
2012-06-13 5:04 ` Chris Samuel [this message]
2012-06-13 14:33 ` Chris Mason
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=4FD81F46.3010702@csamuel.org \
--to=chris@csamuel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=chris.mason@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=oliva@lsd.ic.unicamp.br \
--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).