linux-ext4 - Re: [PATCH 1/5][TAKE2] fallocate() implementation on i86, x86

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] [day] [month] [year] [list]

Message-ID: <20070521053831.GA10269@thunk.org>
Date:	Mon, 21 May 2007 01:38:31 -0400
From:	Theodore Tso <tytso@....edu>
To:	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>
Cc:	cmm@...ibm.com, "Amit K. Arora" <aarora@...ux.vnet.ibm.com>,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 1/5][TAKE2] fallocate() implementation on i86, x86_64 and powerpc

On Sun, May 20, 2007 at 07:39:32AM -0500, Dave Kleikamp wrote:
> On Fri, 2007-05-18 at 16:10 -0700, Mingming Cao wrote:
> > On Fri, 2007-05-18 at 17:36 -0400, Theodore Tso wrote:
> 
> > > We've missed the -rc1 merge window, so the goal should be to make sure
> > > that everything in the series file before the "unstable patches" is
> > > ready for merging.
> > > 
> > I tend to agree.  But there are some bug-fix type or mount option
> > patches that can try to target for rc2, what do you think?
> 
> I agree with Mingming.  There's no reason for these patches not to be in
> mainline.  I am curious why the fallocate patches were put at the top of
> the series file in the first place.  The older patches shouldn't be held
> up by fallocate (which should wait until the next merge window).

I've rebased the ext4 patch queue for 2.6.22-rc2, and moved the
obvious bug fixes to the top of the queue.  There's one patch which I
missed (ext4-free-blocks-on-insert-extent-failure.patch) which is also
a bug fixed, that should be moved up.

It's true that some of the older patches are below fallocate in the
queue, but they are still new features that probably shouldn't be
pushed at this point.  But yes, I agree that the bug fixes should be
pushed to Linus before 2.6.22 ships.

Regards,

						- 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