[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180208144918.GF10945@tassilo.jf.intel.com>
Date: Thu, 8 Feb 2018 06:49:18 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: Jan Kara <jack@...e.cz>
Cc: syzbot <syzbot+283c3c447181741aea28@...kaller.appspotmail.com>,
akpm@...ux-foundation.org, aryabinin@...tuozzo.com,
jlayton@...hat.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, mgorman@...hsingularity.net, mingo@...nel.org,
rgoldwyn@...e.com, syzkaller-bugs@...glegroups.com,
linux-fsdevel@...r.kernel.org
Subject: Re: INFO: task hung in sync_blockdev
> > 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
Powered by blists - more mailing lists