[<prev] [next>] [day] [month] [year] [list]
Date: Tue, 12 Dec 2017 13:27:12 -0800
From: Eric Biggers <ebiggers3@...il.com>
To: syzbot
<bot+e67a4c51cf784b4d739fd8402e6dd0ea296cda5c@...kaller.appspotmail.com>
Cc: adobriyan@...il.com, akinobu.mita@...il.com,
akpm@...ux-foundation.org, dvyukov@...gle.com,
ebiederm@...ssion.com, jpoimboe@...hat.com,
linux-kernel@...r.kernel.org, mingo@...nel.org,
syzkaller-bugs@...glegroups.com, vegard.nossum@...cle.com
Subject: Re: possible deadlock in do_io_accounting
On Mon, Dec 04, 2017 at 10:41:01AM -0800, syzbot wrote:
> syzbot will keep track of this bug report.
> Once a fix for this bug is committed, please reply to this email with:
> #syz fix: exact-commit-title
> To mark this as a duplicate of another syzbot report, please reply with:
> #syz dup: exact-subject-of-another-report
> If it's a one-off invalid bug report, please reply with:
> #syz invalid
> Note: if the crash happens again, it will cause creation of a new
> bug report.
> Note: all commands must start from beginning of the line in the email body.
#syz dup: possible deadlock in seq_read
Powered by blists - more mailing lists