From: Andi Kleen <ak@linux.intel.com>
To: Jan Kara <jack@suse.cz>
Cc: syzbot <syzbot+283c3c447181741aea28@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, aryabinin@virtuozzo.com,
jlayton@redhat.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mgorman@techsingularity.net,
mingo@kernel.org, rgoldwyn@suse.com,
syzkaller-bugs@googlegroups.com, linux-fsdevel@vger.kernel.org
Subject: Re: INFO: task hung in sync_blockdev
Date: Thu, 8 Feb 2018 06:49:18 -0800 [thread overview]
Message-ID: <20180208144918.GF10945@tassilo.jf.intel.com> (raw)
In-Reply-To: <20180208092839.ebe5rk6mtvkk5da4@quack2.suse.cz>
> > It seems multiple processes deadlocked on the bd_mutex.
> > Unfortunately there's no backtrace for the lock acquisitions,
> > so it's hard to see the exact sequence.
>
> Well, all in the report points to a situation where some IO was submitted
> to the block device and never completed (more exactly it took longer than
> those 120s to complete that IO). It would need more digging into the
Are you sure? I didn't think outstanding IO would take bd_mutex.
-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-08 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a11447070ac6fcb0564a08cb1@google.com>
2018-02-07 15:52 ` INFO: task hung in sync_blockdev Andi Kleen
2018-02-08 9:28 ` Jan Kara
2018-02-08 13:28 ` Dmitry Vyukov
2018-02-08 14:08 ` Jan Kara
2018-02-08 14:18 ` Dmitry Vyukov
2018-02-08 16:18 ` Jan Kara
2018-02-08 16:23 ` Andrey Ryabinin
2018-02-08 17:17 ` Dmitry Vyukov
2018-02-09 15:31 ` Andrey Ryabinin
2018-02-08 14:49 ` Andi Kleen [this message]
2018-02-08 16:20 ` 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=20180208144918.GF10945@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=rgoldwyn@suse.com \
--cc=syzbot+283c3c447181741aea28@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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).