linux-kernel - Re: Asking for inclusion of nilfs2 in the mainline kernel

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:	Tue, 10 Mar 2009 15:54:59 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ryusuke Konishi <konishi.ryusuke@....ntt.co.jp>
Cc:	hch@....de, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, konishi.ryusuke@....ntt.co.jp
Subject: Re: Asking for inclusion of nilfs2 in the mainline kernel

On Wed, 11 Mar 2009 01:55:42 +0900 (JST)
Ryusuke Konishi <konishi.ryusuke@....ntt.co.jp> wrote:

> I've been working for the past serveral months to take review comments
> and to continually solve users' problems come up in mainling list

Yes, the maintenance has been impressive.

> (thanks for all giving comments and feedbacks!).  Also, I've tried to
> stabilize API and disk format to restrict additional changes and
> ensure backward compatibility.

Well.  From the point of view of mainline linux, there is no
back-compatibility issue, because the fs hasn't been merged yet.

You perhaps have back-compatibility concerns for existing users of the
out-of-tree patch, but I'd encourage you to not worry about that too
much - there will be fairly few users and they are probably pretty
technical and will be able to cope with a migration.  It's a _bit_ hard
on them but on the other hand, omitting back-compatibility code leads
to a better implementation for the long term.

What you should be more concerned about is forward-compatibility.  What
arrangements do you presently have in place to be able to later alter the
on-disk format without causing too much disruption?  Having a strong
design here will make changes easier to do and will lead to a better
filesystem.

Also..  Don't get _too_ concerned about freezing the on-disk format at
this time.  You could put in a mount-time printk("the nilfs on-disk
format may change at any time - do not place critical data on a nilfs
filesystem") and we leave that in place for a few months while things
stabilise.

And yes, I was planning on sending nilfs in to Linus for 2.6.30 unless
someone has decent-sounding reasons to hold it back.
--
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/