From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Brian Foster <bfoster@redhat.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: avoid firstused overflow in attr3 leaf header with 64k blocks
Date: Tue, 24 Feb 2015 08:58:02 +1100 [thread overview]
Message-ID: <20150223215802.GV4251@dastard> (raw)
In-Reply-To: <54EB8E5D.8080905@sandeen.net>
On Mon, Feb 23, 2015 at 02:32:29PM -0600, Eric Sandeen wrote:
> On 2/23/15 2:07 PM, Brian Foster wrote:
> > The attr3 leaf header has a 16-bit firstused field that tracks the first
> > used entry offset. This field is initialized to the block size in
> > xfs_attr3_leaf_create() and updated accordingly in
> > xfs_attr3_leaf_add_work() when new attributes are added.
> >
> > The initialization of firstused overflows if the block size exceeds
> > 16-bits. E.g., xfstests test generic/117 causes assert failures on a
> > -bsize=64k fs on ppc64 because ichdr.firstused evaluates to 0.
>
> cool :)
>
> > Update the firstused initialization to not exceed the maximum value of
> > an unsigned short. This avoids the overflow to 0 and allows firstused to
> > be updated appropriately on subsequent xattr addition. Also update the
> > freemap size calculation to use the actual block size rather than the
> > potentially minimized version stored in firstused.
>
> I'm a little scared by this; does this truncated value risk going to disk?
> (Yes, I think so.) Is that ok? Does that ... mean we lose a byte of space
> we'd otherwise have? Maybe that's ok ...
>
> FWIW, I think the same problem exists in xfs_attr3_leaf_compact():
>
> /* Initialise the incore headers */
> ichdr_src = *ichdr_dst; /* struct copy */
> ichdr_dst->firstused = args->geo->blksize;
>
> and xfs_attr3_leaf_unbalance():
>
> tmphdr.firstused = state->args->geo->blksize;
And a loop in xfs_attr3_leaf_remove() that does:
tmp = args->geo->blksize;
.....
ichdr.firstused = tmp;
so if the the loop in between does not modify tmp...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-02-23 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 20:07 [PATCH] xfs: avoid firstused overflow in attr3 leaf header with 64k blocks Brian Foster
2015-02-23 20:32 ` Eric Sandeen
2015-02-23 21:58 ` Dave Chinner [this message]
2015-02-24 13:28 ` Brian Foster
2015-02-23 21:53 ` Dave Chinner
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=20150223215802.GV4251@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=sandeen@sandeen.net \
--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 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.