public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Hot topics for the next release
Date: Wed, 06 Aug 2008 11:13:12 -0400	[thread overview]
Message-ID: <1218035592.15342.78.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1218034728.5111.77.camel@pmac.infradead.org>

On Wed, 2008-08-06 at 15:58 +0100, David Woodhouse wrote:
> On Wed, 2008-08-06 at 10:21 -0400, Chris Mason wrote:
> > NFS Support
> 
> This is basically ready. All you need in btrfs is the two patches from
> Balaji Rao, which I've updated to apply to the 0.16 and put in
> git.infradead.org/users/dwmw2/btrfs-kernel-unstable.git (along with a
> build fix for 2.6.27-rc2, which is also below).
> 
> The rest of it is a generic problem with NFSD, for which the (current)
> fix is at git.infradead.org/users/dwmw2/nfsexport-2.6.git
> 
> You could perhaps copy the readdir hack into btrfs code for use with
> obsolete kernels -- but to be honest I'd be inclined to leave that for
> the masochists^Wenterprise folks.
> 

We do need the readdir hack, being able to test on older kernels (say
2.6.26) is a big part of attracting and keeping btrfs testers.

Thanks for the trylock_page, I'll toss it in.

-chris



  reply	other threads:[~2008-08-06 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 14:21 Hot topics for the next release Chris Mason
2008-08-06 14:58 ` David Woodhouse
2008-08-06 15:13   ` Chris Mason [this message]
2008-08-06 15:26     ` Toei Rei
2008-08-06 18:45     ` David Woodhouse
2008-08-06 15:42 ` jim owens
2008-08-06 16:36   ` Chris Mason
2008-08-06 20:36     ` jim owens
2008-08-06 20:43       ` Chris Mason
2008-08-06 20:49         ` Joe Peterson
2008-08-06 20:53           ` 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=1218035592.15342.78.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=dwmw2@infradead.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