[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170110185033.GA58743@gmail.com>
Date: Tue, 10 Jan 2017 10:50:33 -0800
From: Eric Biggers <ebiggers3@...il.com>
To: Roman Penyaev <roman.penyaev@...fitbricks.com>
Cc: Theodore Ts'o <tytso@....edu>, linux-ext4@...r.kernel.org,
Eric Biggers <ebiggers@...gle.com>
Subject: Re: Refreshed rootfs.img for kvm-xfstests
On Tue, Jan 10, 2017 at 01:48:03PM +0100, Roman Penyaev wrote:
>
> I retested the following configurations on 69973b830859 ("Linux 4.9"):
>
> ./kvm-xfstests.sh -c nojournal ext4/301
> ./kvm-xfstests.sh -c ext3conv generic/347
> ./kvm-xfstests.sh -c adv generic/396 generic/399
> ./kvm-xfstests.sh -c data_journal generic/347
> ./kvm-xfstests.sh -c bigalloc generic/399
> ./kvm-xfstests.sh -c bigalloc_1k generic/273
>
> all of the tests from list have failed.
>
> This is not very much helpful, but at least that can be a starting
> point for bisecting.
>
> When there was a successful xfstests run at least for some of
> the configurations? Would be nice to have a "good" reference.
>
Hi Roman,
Generally these have been broken for a while, or in the case of generic/396 and
generic/399 are new tests which are exposing bugs. A few of these I was already
aware of but just haven't had time to get to:
- the failure of generic/347 in data journalling mode is intermittent
- the failure of generic/396 in "adv" mode is related to the use of the inline
data feature, apparently caused by ext4_convert_inline_data() corrupting an
empty directory
- failure of generic/399 in some configurations
If you're interested in looking into any of these failing tests and either
fixing the kernel or fixing the test as appropriate, please feel free to!
Thanks,
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists