From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 204049] [xfstests generic/388]: XFS: Assertion failed: ip->i_d.di_format != XFS_DINODE_FMT_BTREE || ip->i_d.di_nextents > XFS_IFORK_MAXEXT(ip, XFS_DATA_FORK), file: fs/xfs/xfs_inode.c, line: 3646
Date: Fri, 19 Jul 2019 21:29:04 +0000 [thread overview]
Message-ID: <bug-204049-201763-eo3Tgqh1ro@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204049-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204049
--- Comment #5 from Luis Chamberlain (mcgrof@kernel.org) ---
(In reply to Luis Chamberlain from comment #4)
> The crash observed on stable kernels can be fixed with commit 6958d11f77
> ("xfs: don't trip over uninitialized buffer on extent read of corrupted
> inode") merged on v5.1.
>
> I can't reproduce the immediate panic on v5.1 with the
> "xfs_reflink_normapbt" anymore, as such I believe this seems like a
> regression, and you should be able to bisect to v5.1 as the good kernel.
Correction, it just took longer to crash. Same crash as in kz#204223 [0] on
v5.1. That issue is still not fixed.
[0] https://bugzilla.kernel.org/show_bug.cgi?id=204223
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-07-19 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 8:04 [Bug 204049] New: [xfstests generic/388]: XFS: Assertion failed: ip->i_d.di_format != XFS_DINODE_FMT_BTREE || ip->i_d.di_nextents > XFS_IFORK_MAXEXT(ip, XFS_DATA_FORK), file: fs/xfs/xfs_inode.c, line: 3646 bugzilla-daemon
2019-07-18 20:00 ` [Bug 204049] " bugzilla-daemon
2019-07-18 20:19 ` bugzilla-daemon
2019-07-18 20:29 ` bugzilla-daemon
2019-07-19 19:37 ` bugzilla-daemon
2019-07-19 21:29 ` bugzilla-daemon [this message]
2019-07-19 21:37 ` Bill O'Donnell
2019-07-19 21:45 ` bugzilla-daemon
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-204049-201763-eo3Tgqh1ro@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).