From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 203947] [xfstests generic/475]: general protection fault: 0000 [#1] RIP: 0010:xfs_setfilesize_ioend+0xb1/0x220 [xfs]
Date: Sat, 29 Jun 2019 16:07:45 +0000 [thread overview]
Message-ID: <bug-203947-201763-ZoLV7UynfB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203947-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203947
--- Comment #7 from Darrick J. Wong (djwong+kernel@djwong.org) ---
This is a different issue. It would help to know where "xfs_bmapi_read+0x311"
points to in your kernel, though it looks like inode inactivation crashed while
trying to tear down an attr fork, and maybe the attr fork wasn't loaded in
memory? (Possibly because the fs went down while the inode was being set up?)
Ahh generic/475, bringer of much bug report. :)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-06-29 16:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 8:32 [Bug 203947] New: [xfstests generic/475]: general protection fault: 0000 [#1] RIP: 0010:xfs_setfilesize_ioend+0xb1/0x220 [xfs] bugzilla-daemon
2019-06-27 8:35 ` [Bug 203947] " bugzilla-daemon
2019-06-27 18:35 ` bugzilla-daemon
2019-06-27 18:35 ` bugzilla-daemon
2019-06-29 3:30 ` bugzilla-daemon
2019-06-29 3:46 ` bugzilla-daemon
2019-06-29 3:48 ` bugzilla-daemon
2019-06-29 16:07 ` bugzilla-daemon [this message]
2019-06-29 17:31 ` bugzilla-daemon
2019-06-29 17:35 ` bugzilla-daemon
2019-06-30 13:52 ` bugzilla-daemon
2019-07-09 4:30 ` bugzilla-daemon
2019-07-11 22:59 ` bugzilla-daemon
2019-07-12 4:27 ` bugzilla-daemon
2019-07-12 13:18 ` 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-203947-201763-ZoLV7UynfB@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).