From: Jan Kara <jack@suse.cz>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Jan Kara <jack@suse.cz>, linux-xfs@vger.kernel.org
Subject: Re: Deadlock during generic/530 test
Date: Thu, 29 Aug 2019 18:12:45 +0200 [thread overview]
Message-ID: <20190829161245.GA14731@quack2.suse.cz> (raw)
In-Reply-To: <20190829155445.GE5354@magnolia>
On Thu 29-08-19 08:54:45, Darrick J. Wong wrote:
> On Thu, Aug 29, 2019 at 03:31:56PM +0200, Jan Kara wrote:
> > Hello,
> >
> > When running fstests, I've hit a deadlock with generic/530 test with
> > 5.3-rc6 based kernel (commit 9e8312f5e160 in particular) in my test VM.
> > Full dmesg is attached. BTW mount is the only task in D state. In
> > particular all xfs kernel processes are happily sitting in interruptible
> > sleep.
>
> Hm, is this possibly the same as:
>
> https://lore.kernel.org/linux-xfs/20190821110448.30161-1-chandanrlinux@gmail.com/
>
> (Something about needing to nudge the log along when dumping unlinked
> inodes during log recovery?)
Yeah. Looks like that. Thanks for the pointer.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2019-08-29 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 13:31 Deadlock during generic/530 test Jan Kara
2019-08-29 15:54 ` Darrick J. Wong
2019-08-29 16:12 ` 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=20190829161245.GA14731@quack2.suse.cz \
--to=jack@suse.cz \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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