From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs loopback problems
Date: Mon, 07 Jul 2014 18:29:36 +1000 [thread overview]
Message-ID: <1493301.7J9ZoDEm6J@quad> (raw)
In-Reply-To: <53BA11FE.9080101@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
On Mon, 7 Jul 2014 11:20:30 AM Qu Wenruo wrote:
> As Chris Mason mentioned, fixed in the following patch:
> https://patchwork.kernel.org/patch/4143821/
That should probably go to -stable (if it hasn't already), especially as 3.14
is a new LTS kernel.
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
prev parent reply other threads:[~2014-07-07 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-06 10:09 btrfs loopback problems Russell Coker
2014-07-07 3:20 ` Qu Wenruo
2014-07-07 8:29 ` Chris Samuel [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=1493301.7J9ZoDEm6J@quad \
--to=chris@csamuel.org \
--cc=linux-btrfs@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).