linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>,
	Eric Sandeen <sandeen@sandeen.net>, Eryu Guan <eguan@redhat.com>,
	agruenba@redhat.com, btrfs <linux-btrfs@vger.kernel.org>,
	fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: Generic/389 xfs_io segfault on btrfs and ext4
Date: Tue, 10 Jan 2017 20:53:34 -0600	[thread overview]
Message-ID: <c5ea839d-1962-e363-d83b-936328f985df@redhat.com> (raw)
In-Reply-To: <5c56afcd-13b0-d3b3-e18c-0b902691d8f4@cn.fujitsu.com>

On 1/10/17 8:45 PM, Qu Wenruo wrote:
> 
> 
> At 01/11/2017 10:40 AM, Eric Sandeen wrote:

...

>> What version of kernel and xfsprogs were you testing, and what was the segfault?
> 
> Kernel is mainline v4.10-rc1.
> No debuginfo installed, so no backtrace, but since there is so many
> 
> So the problem is the old xfsprogs, I'll update or compile xfsprogs.
> Thanks for your kind info.

Just FWIW, I always have latest xfsprogs in rawhide, but I don't usually push
to other fedoras.

It should be easy to grab
https://kojipkgs.fedoraproject.org/packages/xfsprogs/4.9.0/1.fc26/src/xfsprogs-4.9.0-1.fc26.src.rpm
and rebuild & install.

-Eric


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11  2:08 Generic/389 xfs_io segfault on btrfs and ext4 Qu Wenruo
2017-01-11  2:40 ` Eric Sandeen
2017-01-11  2:45   ` Qu Wenruo
2017-01-11  2:53     ` Eric Sandeen [this message]
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=c5ea839d-1962-e363-d83b-936328f985df@redhat.com \
    --to=sandeen@redhat.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 \
    --cc=quwenruo@cn.fujitsu.com \
    --cc=sandeen@sandeen.net \
    /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).