linux-ext4 - Re: [RFC PATCH 10/17] signed int -> blk64_t to fix bugs at 2^31

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:	Fri, 14 Nov 2008 09:24:33 -0500
From:	Theodore Tso <tytso@....edu>
To:	Valerie Aurora Henson <vaurora@...hat.com>
Cc:	Andreas Dilger <adilger@....com>, linux-ext4@...r.kernel.org
Subject: Re: [RFC PATCH 10/17] signed int -> blk64_t to fix bugs at 2^31 -
	2^32 blocks

On Thu, Nov 13, 2008 at 09:38:12PM -0500, Valerie Aurora Henson wrote:
> 
> Agreed.  Ted, is this a good format for you or do you want me to
> regenerate against something?
> 

No, this is fine.  I'll take the patch and merge it into maint.

Note, what I'm going to try to do is to take entire patches of yours
at once, although in some cases they will be applied to different
branches (or split into different patches).

The goal will be to not disturb things too badly if you do any further
work on the patch series, since git-rebase should be smart enough.
However, it might be a good idea for you to set a tag on what you've
pushed so far, and to save everything past that point as diffs in case
git rebase doesn't work out for whatever reason.

Hopefully while I'm in Japan and/or over Thanksgiving weekend I'll
have enough time to merge all of these patches into mainline.  (I'll
probably miss next week's conference call as well since I'll be in
Tokyo, BTW.  If someone can take notes during the call, or at least
for anything that needs my attention, I'd appreciate it.)

						- 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