linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Eryu Guan <eguan@redhat.com>, <agruenba@redhat.com>,
	btrfs <linux-btrfs@vger.kernel.org>, <fstests@vger.kernel.org>,
	<linux-xfs@vger.kernel.org>
Subject: Generic/389 xfs_io segfault on btrfs and ext4
Date: Wed, 11 Jan 2017 10:08:54 +0800	[thread overview]
Message-ID: <ca7ae533-8d7f-9783-1900-bdfb17d6a32c@cn.fujitsu.com> (raw)

Hi, Andreas and Eryu,

I found test case generic/389 fails on btrfs and ext4, and it fails with 
xfs_io segfault.

So it seems to be a bug in xfsprogs, but I'm already using the latest 
release from Fedora.

Is this a known bug?

Thanks,
Qu



             reply	other threads:[~2017-01-11  2:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11  2:08 Qu Wenruo [this message]
2017-01-11  2:40 ` Generic/389 xfs_io segfault on btrfs and ext4 Eric Sandeen
2017-01-11  2:45   ` Qu Wenruo
2017-01-11  2:53     ` Eric Sandeen
2017-01-11  3:00       ` Qu Wenruo
2017-01-11  3:01         ` Eric Sandeen

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=ca7ae533-8d7f-9783-1900-bdfb17d6a32c@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=agruenba@redhat.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.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).