From: NeilBrown <neilb@suse.de>
To: David Howells <dhowells@redhat.com>
Cc: linux-btrfs@vger.kernel.org, linux-cachefs@redhat.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH/RFC] fscache/cachefiles versus btrfs
Date: Fri, 10 Apr 2015 11:24:31 +1000 [thread overview]
Message-ID: <20150410112431.0e9c337d@notabene.brown> (raw)
In-Reply-To: <29536.1428571388@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
On Thu, 09 Apr 2015 10:23:08 +0100 David Howells <dhowells@redhat.com> wrote:
> NeilBrown <neilb@suse.de> wrote:
>
> > Is there a better way? Could a better way be created? Maybe
> > SEEK_DATA_RELIABLE ??
>
> fiemap() maybe?
>
> > Also, if you do try to use fscache on btrfs with 3.19, then nothing gets
> > cached (as expected) and with a heavy load you can lose a race and get an
> > asserting fail in fscache_enqueue_operation
>
> Do you have the patches here applied?
>
> http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-fixes
>
Do I don't. I had looked through them and while they did seem to be
addressing similar sorts of races, nothing seems like an obvious match.
I haven't been able to reproduce the BUG_ON myself. I only have a report
of it repeatedly affecting someone else:
https://bugzilla.opensuse.org/show_bug.cgi?id=908706
I'll probably have to be happy with fixing usage on btrfs, and hope the other
bug is fixed already or doesn't become a problem.
Thanks,
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-04-10 1:24 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 [this message]
2015-04-20 4:49 ` NeilBrown
2015-04-20 9:27 ` David Howells
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=20150410112431.0e9c337d@notabene.brown \
--to=neilb@suse.de \
--cc=dhowells@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@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).