linux-ext4 - Re: [PATCH 2/2] ext4: Fix compat EXT4_IOC_ADD

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:	Tue, 25 May 2010 11:08:25 -0400
From:	tytso@....edu
To:	Andreas Dilger <andreas.dilger@...cle.com>
Cc:	Ben Hutchings <ben@...adent.org.uk>,
	Andreas Dilger <adilger@....com>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 2/2] ext4: Fix compat EXT4_IOC_ADD_GROUP

On Thu, May 20, 2010 at 10:41:20PM -0600, Andreas Dilger wrote:
> On 2010-05-20, at 17:34, Ben Hutchings wrote:
> > struct ext4_new_group_input needs to be converted because u64 has
> > only 32-bit alignment on some 32-bit architectures, notably i386.
> 
> Sigh, it would have been nice to catch this when ext4_new_group_input was first created.
> 
> I don't mind fixing the kernel, since this is clearly broken.
> However, we may as well go ahead and declare a new struct
> ext4_new_group_input that has the right alignment, rename and
> deprecate the old one (have resize2fs prefer the new one if
> available) and take the old one out in a few years.  I hate this
> business of keeping around old cruft like this forever.

Well, in the long run we need a new ioctl which is compatible with
flex_bg, which means doing multiple groups at once, and letting the
kernel do much more of the work of selecting the block and inode
numbers.  And of course to support 2**64 blocks we need to support the
meta_bg style of resizing.  So we need to do some thinking about how
to support resizing in the long-term anyway.

   	   	       	   	     - 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