linux-ext4 - Re: [LSF/MM TOPIC] Drop ext2/ext3 codebase? When?

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: <AANLkTi=wAX8yLSsbn-zM5t6DrE22asYnz6KdQBfSYuUT@mail.gmail.com>
Date:	Thu, 3 Feb 2011 23:57:25 +0200
From:	Amir Goldstein <amir73il@...il.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Michael Rubin <mrubin@...gle.com>, Jan Kara <jack@...e.cz>,
	lsf-pc@...ts.linuxfoundation.org, linux-fsdevel@...r.kernel.org,
	linux-ext4@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [LSF/MM TOPIC] Drop ext2/ext3 codebase? When?

On Thu, Feb 3, 2011 at 9:49 PM, Eric Sandeen <sandeen@...hat.com> wrote:
>
> On 2/3/11 1:32 PM, Michael Rubin wrote:
> > On Thu, Feb 3, 2011 at 7:08 AM, Eric Sandeen <sandeen@...hat.com> wrote:
> >> If we can have a real plan for moving in this direction though, I'd
> >> support it.  I'm just not sure how we get enough real testing under
> >> our belts to be comfortable with dropping ext[23], especially as
> >> most distros now default to ext4 anyway.
> >
> > Eric what sort of testing are you looking for?
>
> Anything, the more formal or more widespread the better.
>
> I just don't think it's used much this way today...
>
> We can start with xfstests etc but I'd be more concerned about
> unexpected behavioral or performance changes.
>
> > I admit I like having ext2 around for comparisons in bug situations.
> > It really helps to isolate the problem area. How painful is the
> > upkeep?
>
> since ext4 was merged, about 450 commits to ext2 & ext3 files.
>
> since 2.6.32, about 150 commits.
>

Can you give a rough estimate of how those commits diverge between
bugfixes, kernel API changes, code cleanups?

Next3 has been following ext3 since 2.6.31 and I remember changes of
the 2 latter,
but not many major bugfixes.

I hardly think we can get away with throwing out ext3 code base, but
maybe it can go
into bugfixes-only mode? that is unless Jan likes to apply cleanups ;-)

Amir.

> Translating that into pain units, I dunno.  In distro-land, I often
> have bugfixes that need to hit 2 or 3 of the filesystems as well.
>
> -Eric
>
> > mrubin
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> > the body of a message to majordomo@...r.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html