From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: jack@suse.com, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: ext2, possible circular locking dependency detected
Date: Tue, 25 Feb 2020 00:11:20 +0900 [thread overview]
Message-ID: <10329.1582557080@jrobl> (raw)
In-Reply-To: <20200224130219.GE27857@quack2.suse.cz>
Jan Kara:
> OK, in the end I've decided to go with a different solution because I
> realized the warning is a false positive one. The patch has passed a
> fstests run but I'd be grateful if you could verify whether you can no longer
> trigger the lockdep warning. Thanks!
I will.
But it may take very long time, a month or two I am afraid.
If you don't receive any mail about this matter in next few months, then
it means everything is fine.
Thnak you
J. R. Okajima
prev parent reply other threads:[~2020-02-24 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 2:53 ext2, possible circular locking dependency detected J. R. Okajima
2020-02-24 9:08 ` Jan Kara
2020-02-24 10:02 ` J. R. Okajima
2020-02-24 13:02 ` Jan Kara
2020-02-24 15:11 ` J. R. Okajima [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=10329.1582557080@jrobl \
--to=hooanon05g@gmail.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).