From: David Woodhouse <dwmw2@infradead.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Balaji Rao <balajirrao@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] rewrite btrfs_readdir()
Date: Mon, 18 Aug 2008 20:08:03 +0100 [thread overview]
Message-ID: <1219086483.3184.403.camel@pmac.infradead.org> (raw)
In-Reply-To: <1219085216.14063.9.camel@think.oraclecorp.com>
On Mon, 2008-08-18 at 14:46 -0400, Chris Mason wrote:
> It can happen today for the tree of tree roots (directory of
> subvolumes and named snapshots). It happens when the name hashes
> collide. For real directories we use the sequence number index
> instead of the name hash index, so it normally won't happen.
Ok, that's fine then. I've removed the WARN_ON() from the patch in my
git tree. This is what I have outstanding for you at
git://git.infradead.org/users/dwmw2/btrfs-kernel-unstable:
Balaji Rao (2):
Introduce btrfs_iget helper
NFS support for btrfs - v3
David Woodhouse (7):
Implement our own copy of the nfsd readdir hack, for older kernels
Discard sector data in __free_extent()
Remove special cases for "." and ".."
Minor cleanup of btrfs_real_readdir()
Optimise NFS readdir hack slightly; don't call readdir() again when done
Fill f_fsid field in btrfs_statfs()
Mask root object ID into f_fsid in btrfs_statfs()
Makefile | 2 +-
compat.h | 17 ++++
ctree.h | 2 +
export.c | 208 +++++++++++++++++++++++++++++++++++++++++++++++
export.h | 19 +++++
extent-tree.c | 25 ++++++
inode.c | 250 +++++++++++++++++++++++++++++++++++++-------------------
super.c | 12 +++
8 files changed, 449 insertions(+), 86 deletions(-)
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2008-08-18 19:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 20:31 [PATCH] NFS support for btrfs - v2 Balaji Rao
2008-08-17 11:53 ` David Woodhouse
2008-08-17 12:51 ` Balaji Rao
2008-08-17 12:56 ` David Woodhouse
2008-08-17 13:24 ` Balaji Rao
2008-08-17 13:30 ` David Woodhouse
2008-08-17 14:17 ` David Woodhouse
2008-08-17 16:10 ` [PATCH] rewrite btrfs_readdir() David Woodhouse
2008-08-18 18:46 ` Chris Mason
2008-08-18 19:08 ` David Woodhouse [this message]
2008-08-18 19:24 ` Chris Mason
2008-08-18 19:32 ` David Woodhouse
2008-08-17 13:40 ` [PATCH] NFS support for btrfs - v2 David Woodhouse
2008-08-18 19:23 ` Chris Mason
2008-08-18 19:33 ` David Woodhouse
2008-08-18 19:47 ` Chris Mason
2008-08-18 20:20 ` David Woodhouse
2008-08-18 20:32 ` Chris Mason
2008-08-18 21:52 ` David Woodhouse
2008-08-19 11:54 ` Chris Mason
2008-08-19 14:49 ` David Woodhouse
2008-08-19 21:34 ` David Woodhouse
2008-08-19 0:16 ` Christoph Hellwig
2008-08-19 0:21 ` David Woodhouse
2008-08-18 11:51 ` David Woodhouse
2008-08-18 12:10 ` David Woodhouse
2008-08-18 19:15 ` 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=1219086483.3184.403.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=balajirrao@gmail.com \
--cc=chris.mason@oracle.com \
--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