From: "J. Bruce Fields" <bfields@fieldses.org>
To: Sage Weil <sage@inktank.com>
Cc: torvalds@linux-foundation.org, ceph-devel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Ceph updates for 3.8
Date: Fri, 21 Dec 2012 13:55:01 -0500 [thread overview]
Message-ID: <20121221185501.GA28092@fieldses.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1212201319500.16508@cobra.newdream.net>
On Thu, Dec 20, 2012 at 01:29:49PM -0800, Sage Weil wrote:
> Hi Linus,
>
> Please pull the following Ceph updates for 3.8 from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
>
> There's a trivial conflict in net/ceph/osd_client.c dealing with rbtree
> node initialization; the resolution is to keep the RB_CLEAR_NODE() call
> (see 4c199a93 for the conflicting commit).
>
> There are a few different groups of commits here. The largest is Alex's
> ongoing work to enable the coming RBD features (cloning, striping).
> There is some cleanup in libceph that goes along with it. Cyril and David
> have fixed some problems with NFS reexport (leaking dentries and page
> locks),
Just out of curiosity--what's the state of NFS exports now?
I seem to recall initially it was sort-of supported by filehandle
lookups didn't really work reliably?
--b.
> and there is a batch of patches from Yan fixing problems with the
> fs client when running against a clustered MDS. There are a few bug fixes
> mixed in for good measure, many of which will be going to the stable trees
> once they're upstream.
>
> My apologies for the late pull. There is still a gremlin in the rbd
> map/unmap code and I was hoping to include the fix for that as well, but
> we haven't been able to confirm the fix is correct yet; I'll send that in
> a separate pull once it's nailed down.
next prev parent reply other threads:[~2012-12-21 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 21:29 [GIT PULL] Ceph updates for 3.8 Sage Weil
2012-12-21 18:55 ` J. Bruce Fields [this message]
2012-12-21 18:59 ` Sage Weil
2013-01-02 17:56 ` J. Bruce Fields
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=20121221185501.GA28092@fieldses.org \
--to=bfields@fieldses.org \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@inktank.com \
--cc=torvalds@linux-foundation.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