linux-kernel - Re: [GIT PULL] Ceph updates for 3.8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 Dec 2012 13:55:01 -0500
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Sage Weil <sage@...tank.com>
Cc:	torvalds@...ux-foundation.org, ceph-devel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Ceph updates for 3.8

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/