From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to f368b29ba917
Date: Sat, 16 Nov 2019 10:15:05 -0800 [thread overview]
Message-ID: <20191116181505.GA15462@infradead.org> (raw)
In-Reply-To: <20191116070236.GA30357@infradead.org>
On Fri, Nov 15, 2019 at 11:02:36PM -0800, Christoph Hellwig wrote:
> FYI, this crash for me in xfs/348 with unfortunately a completely
> garbled dmesg. The xfs-5.5-merge-11 is fine.
git-bisect points to:
xfs: convert open coded corruption check to use XFS_IS_CORRUPT
next prev parent reply other threads:[~2019-11-16 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 18:16 [ANNOUNCE] xfs-linux: for-next updated to f368b29ba917 Darrick J. Wong
2019-11-16 7:02 ` Christoph Hellwig
2019-11-16 18:15 ` Christoph Hellwig [this message]
2019-11-16 19:40 ` Darrick J. Wong
2019-11-16 20:02 ` Darrick J. Wong
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=20191116181505.GA15462@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--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).