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:	Mon, 14 Feb 2011 18:25:04 +0100
From:	Jan Kara <jack@...e.cz>
To:	Amir Goldstein <amir73il@...il.com>
Cc:	Jan Kara <jack@...e.cz>, Michael Rubin <mrubin@...gle.com>,
	Eric Sandeen <sandeen@...hat.com>,
	lsf-pc@...ts.linuxfoundation.org, linux-fsdevel@...r.kernel.org,
	linux-ext4@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Theodore Tso <tytso@....edu>
Subject: Re: [LSF/MM TOPIC] Drop ext2/ext3 codebase? When?

On Sat 12-02-11 13:05:02, Amir Goldstein wrote:
> On Fri, Feb 4, 2011 at 3:17 PM, Jan Kara <jack@...e.cz> wrote:
> >
> > On Thu 03-02-11 11:32:01, 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?
> > I believe Ted wrote a good summary of what combinations of options would
> > need to be tested on a regular basis to get at least some confidence that
> > the switch could work.
> 
> So the problem is that people don'y have much incentive to test "ext3
> mode" as long as they have, well, ext3.
> 
> I can offer an incentive in the form of snapshots support, which may
> appeal for some users, to whom performance improvements is not a good
> enough reason to upgrade their fs.
> 
> Most conveniently, ext4 snapshots is short of extents and delalloc
> support at the moment, but the rest of the code, which was ported from
> next3 is ready to be stabilized/cleaned up for submission.
> 
> So it can be claimed, that pursuing my cause, of pushing the snapshots
> feature for early testers as soon as possible (i.e. before extent
> move-on-write implementation), may also be beneficial to the cause of
> getting "ext3 mode" tested by a larger number of users.
> 
> What do you say, Jan. Do you think that some of your upgrading
> customers could be lured into using ext4 code if we offer them
> snapshots in "ext3 mode"?
  Well, some people might be interested in snapshotting and might move to
ext4 for that reason but these would be mostly people installing new
systems anyway, not the ones just updating older systems. So I don't feel
this would be a major game changer... 

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ