All of lore.kernel.org
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Andreas Dilger <andreas.dilger@oracle.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	Andreas Dilger <adilger@sun.com>,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/2] ext4: Fix compat EXT4_IOC_ADD_GROUP
Date: Tue, 25 May 2010 11:08:25 -0400	[thread overview]
Message-ID: <20100525150824.GK5556@thunk.org> (raw)
In-Reply-To: <63042D4C-90AA-4A3D-A5DC-C0ADF4BF9DDE@oracle.com>

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

  reply	other threads:[~2010-05-25 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 23:30 [PATCH 1/2] ext4: Conditionally define compat ioctl numbers Ben Hutchings
2010-05-20 23:34 ` [PATCH 2/2] ext4: Fix compat EXT4_IOC_ADD_GROUP Ben Hutchings
2010-05-21  4:41   ` Andreas Dilger
2010-05-25 15:08     ` tytso [this message]
2010-05-25 15:25   ` tytso
2010-05-25 15:15 ` [PATCH 1/2] ext4: Conditionally define compat ioctl numbers tytso
2010-05-25 15:22   ` tytso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100525150824.GK5556@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@sun.com \
    --cc=andreas.dilger@oracle.com \
    --cc=ben@decadent.org.uk \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.