From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201577] [xfstests generic/070]: XFS corruption and Oops when setxattr on 64k blocksize XFS
Date: Fri, 07 Dec 2018 17:07:15 +0000 [thread overview]
Message-ID: <bug-201577-201763-Rh7Cf4mEYP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201577-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201577
Eric Sandeen (sandeen@sandeen.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@sandeen.net
--- Comment #3 from Eric Sandeen (sandeen@sandeen.net) ---
Dave's patch
[PATCH] xfs: fix overflow in xfs_attr3_leaf_verify
should fix the verifier failure but I think the OOPS is a separate problem that
still needs to be addressed.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-12-07 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 7:34 [Bug 201577] New: [xfstests generic/070]: XFS corruption and Oops when setxattr on 64k blocksize XFS bugzilla-daemon
2018-10-31 22:42 ` Dave Chinner
2018-10-31 22:42 ` [Bug 201577] " bugzilla-daemon
2018-11-01 1:40 ` bugzilla-daemon
2018-12-07 17:07 ` bugzilla-daemon [this message]
2020-06-10 3:38 ` 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-201577-201763-Rh7Cf4mEYP@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.