linux-kernel - Re: [GIT PULL] ext4 updates for 3.11

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130703235444.GF4072@dastard>
Date:	Thu, 4 Jul 2013 09:54:44 +1000
From:	Dave Chinner <david@...morbit.com>
To:	"Dilger, Andreas" <andreas.dilger@...el.com>
Cc:	Greg KH <greg@...ah.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Theodore Ts'o <tytso@....edu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Drokin, Oleg" <oleg.drokin@...el.com>
Subject: Re: [GIT PULL] ext4 updates for 3.11

On Wed, Jul 03, 2013 at 06:40:40PM +0000, Dilger, Andreas wrote:
> On 2013/03/07 12:12 PM, "Greg KH" <greg@...ah.com> wrote:
> >On Wed, Jul 03, 2013 at 01:29:41PM +1000, Dave Chinner wrote:
> >> On Tue, Jul 02, 2013 at 06:01:11PM -0700, Greg KH wrote:
> >> > For this filesystem, it seems that they don't have any
> >> > resources to do this work and are relying on the community to
> >> > help out.  Which is odd, but big companies are strange some
> >> > times...
> >> 
> >> Didn't we learn this lesson already with POHMELFS? i.e. that
> >> dumping filesystem code in staging on the assumption "the
> >> community" will fix it up when nobody in "the community" uses
> >> or can even test that filesystem is a broken development
> >> model....
> >
> >They (Intel) has said that they will continue to clean up this
> >code in the tree, until it is in good enough shape to be merged
> >into fs/ properly.  If they ever stop helping out, I will end up
> >dropping it from the tree, just like I did for pohmelfs, so don't
> >worry about it lingering around abandoned.
> 
> Right, we are going to continue working on cleaning the code at a
> steady pace until it is ready to move to fs/.  I don't expect Al
> or Dave or Christoph to spend their time (or make their eyes
> bleed) with the current state of the code.  It has already
> undergone some significant cleanup, but needs a bunch more still.

The issue I'm more concerned about is more to do with what happens
when we do something that affects all filesystems, such as API
changes. Then we are forced to look at it and to try to work out
what the hell is going on. This was the real problem with pomelhfs
being in staging - it had an unreasonably high maintenance overhead
compared to other filesystems.

This was mainly because pohelmfs was effectively dumped in staging
and then left unmaintained - if there's consistent effort put into
the Lustre code to clean it up, maintain it and help with API
transitions, then I have nothing to object to and I'll just crawl
back into my box. ;)

Cheers,

Dave.
-- 
Dave Chinner
david@...morbit.com
--
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/