From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 204223] [fstests generic/388 on xfs]: 4.19.58 xfs_nocrc / xfs_reflink null pointer dereference at xfs_trans_brelse+0x21
Date: Thu, 18 Jul 2019 20:22:30 +0000 [thread overview]
Message-ID: <bug-204223-201763-pS4eUG2bzs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204223-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204223
--- Comment #4 from Luis Chamberlain (mcgrof@kernel.org) ---
(In reply to Luis Chamberlain from comment #3)
> kz#204049 reveals upstream is also affected by this bug then.
To be clear, but with a different output, so different issue, and Zorro would
have to test other configurations to see if the same issue creeps up on
upstream with them as well.
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
next prev parent reply other threads:[~2019-07-18 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 19:03 [Bug 204223] 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 19:08 ` [Bug 204223] [xfstests generic/388]: 4.19.58 xfs_nocrc XFS: null pointer dereference at xfs_trans_brelse+0x21 bugzilla-daemon
2019-07-18 19:32 ` [Bug 204223] [fstests generic/388 on xfs]: 4.19.58 xfs_nocrc / xfs_reflink " bugzilla-daemon
2019-07-18 20:21 ` bugzilla-daemon
2019-07-18 20:22 ` bugzilla-daemon [this message]
2019-07-19 3:26 ` bugzilla-daemon
2019-07-19 19:35 ` bugzilla-daemon
2019-07-19 19:35 ` bugzilla-daemon
2019-07-19 21:28 ` bugzilla-daemon
2019-07-20 22:49 ` 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-204223-201763-pS4eUG2bzs@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.