From: David Howells <dhowells@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: dhowells@redhat.com, linux-btrfs@vger.kernel.org,
linux-cachefs@redhat.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH/RFC] fscache/cachefiles versus btrfs
Date: Mon, 20 Apr 2015 10:27:57 +0100 [thread overview]
Message-ID: <31056.1429522077@warthog.procyon.org.uk> (raw)
In-Reply-To: <20150420144956.1f489f67@notabene.brown>
NeilBrown <neilb@suse.de> wrote:
> I managed to reproduce the bug, and when I applied your patches I cannot any
> more. So it looks like you've fixed it - thanks.
I hope so too. Now I just hope Linus takes the patches.
> That just leave the bmap issue. I'll post a patch which causes lseek to be
> used when the fs says that is OK.
Okay, thanks.
David
next prev parent reply other threads:[~2015-04-20 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 7:49 [PATCH/RFC] fscache/cachefiles versus btrfs NeilBrown
2015-04-09 9:23 ` David Howells
2015-04-09 23:52 ` Dave Chinner
2015-04-10 0:42 ` NeilBrown
2015-04-10 1:08 ` Dave Chinner
2015-04-10 1:24 ` NeilBrown
2015-04-20 4:49 ` NeilBrown
2015-04-20 9:27 ` David Howells [this message]
2015-04-10 13:28 ` David Howells
2015-04-13 17:30 ` Christoph Hellwig
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=31056.1429522077@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@suse.de \
/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).