linux-ext4 - Re: Review of ext4-online-defrag-check-for-freespace-fragmentation.patch

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:	Sat, 13 Sep 2008 22:10:24 -0400
From:	Theodore Tso <tytso@....EDU>
To:	a-fujita@...jp.nec.com
Cc:	Takashi Sato <t-sato@...jp.nec.com>, linux-ext4@...r.kernel.org
Subject: Re: Review of
	ext4-online-defrag-check-for-freespace-fragmentation.patch

On Sat, Sep 13, 2008 at 06:16:42PM -0400, Theodore Ts'o wrote:
> 
> Secondly, some of the ioctl numbers chosen by the defrag patches overlap
> other, already existing patches.  This is something we will need to fix,
> long term.  For now, folks should know that we can't count on the ioctl
> numbers being stable, since we will probably need to move them.

Note: I have done this in the version of the defrag patches in the
ext4 patch queue, where all of the ioctl's introduced by the defrag
patches have been renumbered starting at 15, to avoid conflicts with
other ioctls that either exist already or could be introduced in the
future.

If you don't mind, we can also merge up some of the patches that have
been inserted in the patch queue, and then you can start working from
the modified version in the patch queue.  The other way to move
forward is that we can start creating new ioctl's that are more
general and have carefully designed interfaces, and then as the
replacement ioctl's are created, the defrag patches can be shortened
and the on-line defrag command modified to use the new ioctl's.

						- Ted
--
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