From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: bump INUMBERS cursor correctly in xfs_inumbers_walk
Date: Tue, 9 Jul 2019 10:25:38 -0400 [thread overview]
Message-ID: <20190709142538.GA58362@bfoster> (raw)
In-Reply-To: <20190709142226.GP1404256@magnolia>
On Tue, Jul 09, 2019 at 07:22:26AM -0700, Darrick J. Wong wrote:
> On Tue, Jul 09, 2019 at 06:59:43AM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > There's a subtle unit conversion error when we increment the INUMBERS
> > cursor at the end of xfs_inumbers_walk. If there's an inode chunk at
> > the very end of the AG /and/ the AG size is a perfect power of two, that
> > means we can have inodes, that means that the startino of that last
>
> "...is a perfect power of two, the startino of that last chunk..."
>
Yeah, was going to point out this looked like some stale/spurious
text... :P
> --D
>
> > chunk (which is in units of AG inodes) will be 63 less than (1 <<
> > agino_log). If we add XFS_INODES_PER_CHUNK to the startino, we end up
> > with a startino that's larger than (1 << agino_log) and when we convert
> > that back to fs inode units we'll rip off that upper bit and wind up
> > back at the start of the AG.
> >
> > Fix this by converting to units of fs inodes before adding
> > XFS_INODES_PER_CHUNK so that we'll harmlessly end up pointing to the
> > next AG.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
Otherwise looks good:
Reviewed-by: Brian Foster <bfoster@redhat.com>
> > fs/xfs/xfs_itable.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/xfs/xfs_itable.c b/fs/xfs/xfs_itable.c
> > index cda8ae94480c..a8a06bb78ea8 100644
> > --- a/fs/xfs/xfs_itable.c
> > +++ b/fs/xfs/xfs_itable.c
> > @@ -338,15 +338,14 @@ xfs_inumbers_walk(
> > .xi_version = XFS_INUMBERS_VERSION_V5,
> > };
> > struct xfs_inumbers_chunk *ic = data;
> > - xfs_agino_t agino;
> > int error;
> >
> > error = ic->formatter(ic->breq, &inogrp);
> > if (error && error != XFS_IBULK_ABORT)
> > return error;
> >
> > - agino = irec->ir_startino + XFS_INODES_PER_CHUNK;
> > - ic->breq->startino = XFS_AGINO_TO_INO(mp, agno, agino);
> > + ic->breq->startino = XFS_AGINO_TO_INO(mp, agno, irec->ir_startino) +
> > + XFS_INODES_PER_CHUNK;
> > return error;
> > }
> >
prev parent reply other threads:[~2019-07-09 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 13:59 [PATCH] xfs: bump INUMBERS cursor correctly in xfs_inumbers_walk Darrick J. Wong
2019-07-09 14:22 ` Darrick J. Wong
2019-07-09 14:25 ` Brian Foster [this message]
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=20190709142538.GA58362@bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox