linux-kernel - Re: [PATCH 00/21] ceph: Ceph distributed file system client v0.9

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]

Message-ID: <Pine.LNX.4.64.0906191558440.7980@cobra.newdream.net>
Date:	Fri, 19 Jun 2009 16:12:51 -0700 (PDT)
From:	Sage Weil <sage@...dream.net>
To:	Greg KH <greg@...ah.com>
cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 00/21] ceph: Ceph distributed file system client v0.9

On Fri, 19 Jun 2009, Greg KH wrote:
> On Fri, Jun 19, 2009 at 03:31:21PM -0700, Sage Weil wrote:
> > This is a patch series for v0.9 of the Ceph distributed file system
> > client (against v2.6.30).
> 
> Oh, one other question, why put this in staging?  What is keeping it
> being accepted into fs/ like normal?

I would obviously prefer that route, but my assumption has been that the 
code needs some review and a core developer to sign off on it before that 
can happen.  I've posted the patchset a few times now, and haven't gotten 
much response.  If there is something else I can or should be doing to 
push this upstream, I'm all ears...

The code certainly isn't ready for production, but the client code at 
least has seen relatively few changes recently.  Our internal testing is 
ramping up in scale and so far we're primarily working out problems with 
the server side daemons.  

I'm not quite sure what the criteria for mainline inclusion is, as it 
seems to vary from file system to file system, but from my perspective 
any move upstream can only help.

sage
--
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/