From: Jan Kara <jack@suse.cz>
To: Eric Whitney <enwlinux@gmail.com>
Cc: linux-ext4@vger.kernel.org, jack@suse.cz
Subject: Re: generic/232 test failures on 4.14-rc1
Date: Mon, 25 Sep 2017 15:59:46 +0200 [thread overview]
Message-ID: <20170925135946.GB8004@quack2.suse.cz> (raw)
In-Reply-To: <20170921154846.re5vcyn3bugdbie5@localhost.localdomain>
On Thu 21-09-17 11:48:46, Eric Whitney wrote:
> I'm seeing generic/232 fail from time to time when running a 4.14-rc1 kernel
> on xfstest-bld's most recent kvm-xfstests test appliance. In one set of
> trials, it failed in the same manner 4 out of 10 times when running the 4k test
> configuration for ext4.
>
> The failure bisects to "quota: Do not acquire dqio_sem for dquot overwrites in
> v2 format" (ab2b86360f6e). When this patch was reverted in a 4.14-rc1 kernel,
> the failure did not reoccur in a series of 20 trials.
Thanks for debugging this! I'd just note that the commit hash of that
change is different for me - d2faa415166b2883428efa92f451774ef44373ac.
> Example output from the failed test:
>
> QA output created by 232
>
> Testing fsstress
>
> seed = S
> Comparing user usage
> 218a219
> > #3740 -- 4 0 0 1 0 0
> 245a247
> > #45 -- 0 0 0 1 0 0
>
> Note: I'm also seeing a similar failure for generic/233, but the patch
> containing the root cause likely comes somewhere after ab2b86360f6e. I'll post
> another bug report once I locate it.
I'll try to debug this further. Thanks for report!
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-09-25 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 15:48 generic/232 test failures on 4.14-rc1 Eric Whitney
2017-09-25 13:59 ` Jan Kara [this message]
2017-09-26 12:58 ` Jan Kara
2017-09-26 21:41 ` Eric Whitney
2017-09-27 9:34 ` Jan Kara
2017-09-27 1:19 ` Darrick J. Wong
2017-09-27 9:33 ` Jan Kara
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=20170925135946.GB8004@quack2.suse.cz \
--to=jack@suse.cz \
--cc=enwlinux@gmail.com \
--cc=linux-ext4@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