From: Jan Kara <jack@suse.cz>
To: Ritesh Harjani <riteshh@linux.ibm.com>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>,
Eric Whitney <enwlinux@gmail.com>, Theodore Ts'o <tytso@mit.edu>
Subject: Re: xfstests global-ext4/1k generic/219 failure due to dmesg warning of "circular locking dependency detected"
Date: Mon, 12 Oct 2020 13:50:01 +0200 [thread overview]
Message-ID: <20201012115001.GD23665@quack2.suse.cz> (raw)
In-Reply-To: <20201012110347.GB23665@quack2.suse.cz>
On Mon 12-10-20 13:03:47, Jan Kara wrote:
> Hi!
>
> On Fri 09-10-20 22:59:13, Ritesh Harjani wrote:
> > While running generic/219 fstests on a 1k blocksize on x86 box, I see
> > below dmesg warning msg and generic/219 fails. I haven't yet analyzed
> > it, but I remember I have seen such warnings before as well in my testing.
> > I was wondering if others have also seen it in their testing or not and
> > if this is any known issue?
>
> I don't remember seeing this lately. What mkfs options do you use for your
> test? I can see below that mount options are apparently:
>
> acl,user_xattr,block_validity,usrquota,grpquota
BTW, I've tried and the problem indeed does *not* reproduce in my test KVM
setup with 1k block size and default mkfs options. But it does reproduce
with mkfs option "-O quota". So it indeed seems the lockdep annotation is
somehow broken in this config. I'll have a look...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2020-10-12 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 17:29 xfstests global-ext4/1k generic/219 failure due to dmesg warning of "circular locking dependency detected" Ritesh Harjani
2020-10-09 20:12 ` Eric Whitney
2020-10-09 20:24 ` Darrick J. Wong
2020-10-12 11:35 ` Jan Kara
2020-10-12 11:03 ` Jan Kara
2020-10-12 11:50 ` Jan Kara [this message]
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=20201012115001.GD23665@quack2.suse.cz \
--to=jack@suse.cz \
--cc=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=riteshh@linux.ibm.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.