At 01/11/2017 10:53 AM, Eric Sandeen wrote:
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
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
On 1/10/17 8:08 PM, Qu Wenruo wrote:
> Hi, Andreas and Eryu,
>
> I found test case generic/389 fails on btrfs and ext4, and it fails with
> xfs_io segfault.
Details, please?
Works ok here:
# ./check generic/389
FSTYP -- ext4
PLATFORM -- Linux/x86_64 bp-05 4.9.0-rc1+
MKFS_OPTIONS
At 01/11/2017 10:40 AM, Eric Sandeen wrote:
On 1/10/17 8:08 PM, Qu Wenruo wrote:
Hi, Andreas and Eryu,
I found test case generic/389 fails on btrfs and ext4, and it fails with xfs_io
segfault.
Details, please?
Works ok here:
# ./check generic/389
FSTYP -- ext4
PLATFORM --
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
--
To unsubscribe from this list: send the line
