From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 210535] [xfstests generic/466] XFS: Assertion failed: next_agino == irec->ir_startino + XFS_INODES_PER_CHUNK, file: fs/xfs/xfs_iwalk.c, line: 366
Date: Tue, 08 Dec 2020 17:13:26 +0000 [thread overview]
Message-ID: <bug-210535-201763-o3dDJy6ulb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210535-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210535
--- Comment #5 from Zorro Lang (zlang@redhat.com) ---
(In reply to darrick.wong from comment #3)
> On Mon, Dec 07, 2020 at 05:14:26PM +0000,
> bugzilla-daemon@bugzilla.kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=210535
> >
> > Bug ID: 210535
> > Summary: [xfstests generic/466] XFS: Assertion failed:
> > next_agino == irec->ir_startino +
> > XFS_INODES_PER_CHUNK, file: fs/xfs/xfs_iwalk.c, line:
> > 366
> > Product: File System
> > Version: 2.5
> > Kernel Version: xfs-linux xfs-5.10-fixes-7
> > Hardware: All
> > OS: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: normal
> > Priority: P1
> > Component: XFS
> > Assignee: filesystem_xfs@kernel-bugs.kernel.org
> > Reporter: zlang@redhat.com
> > Regression: No
> >
> > Created attachment 294021 [details]
> > --> https://bugzilla.kernel.org/attachment.cgi?id=294021&action=edit
> > generic-466.full
> >
> > xfstests generic/466 hit below assertion failure on power9 ppc64le:
> >
> > [16404.196161] XFS: Assertion failed: next_agino == irec->ir_startino +
> > XFS_INODES_PER_CHUNK, file: fs/xfs/xfs_iwalk.c, line: 366
>
> Does this patch fix it?
>
> --D
>
> From: Darrick J. Wong <darrick.wong@oracle.com>
> Subject: [PATCH] xfs: fix the forward progress assertion in
> xfs_iwalk_run_callbacks
>
> In commit 27c14b5daa82 we started tracking the last inode seen during an
> inode walk to avoid infinite loops if a corrupt inobt record happens to
> have a lower ir_startino than the record preceeding it. Unfortunately,
> the assertion trips over the case where there are completely empty inobt
> records (which can happen quite easily on 64k page filesystems) because
> we advance the tracking cursor without actually putting the empty record
> into the processing buffer. Fix the assert to allow for this case.
>
> Reported-by: zlang@redhat.com
> Fixes: 27c14b5daa82 ("xfs: ensure inobt record walks always make forward
> progress")
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> fs/xfs/xfs_iwalk.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_iwalk.c b/fs/xfs/xfs_iwalk.c
> index 2a45138831e3..eae3aff9bc97 100644
> --- a/fs/xfs/xfs_iwalk.c
> +++ b/fs/xfs/xfs_iwalk.c
> @@ -363,7 +363,7 @@ xfs_iwalk_run_callbacks(
> /* Delete cursor but remember the last record we cached... */
> xfs_iwalk_del_inobt(tp, curpp, agi_bpp, 0);
> irec = &iwag->recs[iwag->nr_recs - 1];
> - ASSERT(next_agino == irec->ir_startino + XFS_INODES_PER_CHUNK);
> + ASSERT(next_agino >= irec->ir_startino + XFS_INODES_PER_CHUNK);
>
> error = xfs_iwalk_ag_recs(iwag);
> if (error)
I just tested on the same P9 machine which reproduced this bug, generic/466
test passed with this patch
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2020-12-08 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 17:14 [Bug 210535] New: [xfstests generic/466] XFS: Assertion failed: next_agino == irec->ir_startino + XFS_INODES_PER_CHUNK, file: fs/xfs/xfs_iwalk.c, line: 366 bugzilla-daemon
2020-12-07 17:14 ` [Bug 210535] " bugzilla-daemon
2020-12-07 17:16 ` bugzilla-daemon
2020-12-07 18:52 ` [Bug 210535] New: " Darrick J. Wong
2020-12-07 18:52 ` [Bug 210535] " bugzilla-daemon
2020-12-08 17:10 ` bugzilla-daemon
2020-12-08 17:13 ` bugzilla-daemon [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=bug-210535-201763-o3dDJy6ulb@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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 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.