From: David Chinner <dgc@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Chinner <dgc@sgi.com>, xfs-dev <xfs-dev@sgi.com>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: [patch] detect and correct bad features2 superblock field
Date: Fri, 22 Feb 2008 09:49:28 +1100 [thread overview]
Message-ID: <20080221224928.GE155407@sgi.com> (raw)
In-Reply-To: <20080220191328.GB24257@infradead.org>
On Wed, Feb 20, 2008 at 02:13:28PM -0500, Christoph Hellwig wrote:
> On Wed, Feb 20, 2008 at 04:40:41PM +1100, David Chinner wrote:
> > There is a bug in mkfs.xfs that can result in writing the features2
> > field in the superblock to the wrong location. This only occurs
> > on some architectures, typically those with 32 bit userspace and
> > 64 bit kernels.
>
> Well, we don't use different ABIs for kernel vs userspace so some
> kernels will get it wrong aswell, you just won't notice until moving
> to a different box because userspace is the same.
True.
> > +
> > + /* must be padded to 64 bit alignment */
> > } xfs_dsb_t;
>
> I'm pretty sure there is some gcc __packed__ magic to enfore that,
> might it be worth to poke some gcc experts to add it?
Yes, it's probably the right thing to do. However, if we are going
to "pack" disk structures, I'd like to do that all in one series
of patches rather than mixed up in other fixes....
> But the actual patch looks fine, ACK from me.
Thanks.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-02-21 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 5:40 [patch] detect and correct bad features2 superblock field David Chinner
2008-02-20 14:09 ` Eric Sandeen
2008-02-20 19:13 ` Christoph Hellwig
2008-02-21 22:49 ` David Chinner [this message]
2008-03-29 3:25 ` Eric Sandeen
2008-03-29 16:19 ` Eric Sandeen
2008-03-30 1:30 ` Eric Sandeen
2008-03-30 1:49 ` Eric Sandeen
2008-03-30 4:50 ` Josef 'Jeff' Sipek
2008-03-30 4:53 ` Eric Sandeen
2008-03-30 5:29 ` Josef 'Jeff' Sipek
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=20080221224928.GE155407@sgi.com \
--to=dgc@sgi.com \
--cc=hch@infradead.org \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox