linux-ext4 - Re: writev corruption and 64-bit quota patches for 2.6.33-rc1?

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: <20091208212109.GT27692@thunk.org>
Date:	Tue, 8 Dec 2009 16:21:09 -0500
From:	tytso@....edu
To:	Jan Kara <jack@...e.cz>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: writev corruption and 64-bit quota patches for 2.6.33-rc1?

On Tue, Dec 08, 2009 at 12:00:43PM +0100, Jan Kara wrote:
>   Hi Ted,
> 
>   do you plan on merging my fixes for writev filesystem corruption and
> 64-bit quota patches? The writev patch is independent of any other patch
> and should go in ASAP, 64-bit quota patch depends on generic quota code
> change so either I can merge it or you can merge a bit later (it's a small
> change for ext4).

Why don't I take the writev patch, and let you merge the 64-bit quota
patch along with the generic quota changes?  Does that make sense?

The only thing that worries me a tiny bit is that there are some quota
bug fixes which the OpenVZ folks have submitted, that I need to review
and haven't gotten to yet, and there's a chance they may conflict with
your 64-bit ext4 quota changes.  But I'm sure we can deal with any
potential merge conflicts should they come up.

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