linux-ext4 - Re: [PATCH 0/8][e2fsprogs] 64-bit block number support

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:	Wed, 17 Oct 2007 16:13:50 +0200
From:	Valerie Clement <valerie.clement@...l.net>
To:	Theodore Tso <tytso@....edu>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH 0/8][e2fsprogs] 64-bit block number support - first part

Theodore Tso wrote:
> It's good to clean this up, but this presumes that blk_t is going to
> change to a 64-bit type.  I'd much rather *add* a blk64_t, and keep
> blk_t at 32 bits.  This patch series in a number of places makes the
> presumption that blk_t will change size --- in particular when it
> creates new interfaces that returns 64-bits through a blk_t.  Please
> don't do that.

Does it mean that we'll have to duplicate all of the structures
containing fields of type blk_t (like process_block_struct,
e2fsck_struct, ext2_inode_cache, ...) and also duplicate most of
the code for the functions which use variables of type blk_t?

   Valérie
-
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