* Re: possible deadlock in proc_pid_attr_write
[not found] <94eb2c03c9bc149d61055fe5f7ae@google.com>
@ 2017-12-12 22:00 ` Eric Biggers
0 siblings, 0 replies; only message in thread
From: Eric Biggers @ 2017-12-12 22:00 UTC (permalink / raw)
To: syzbot
Cc: adobriyan, akinobu.mita, akpm, dvyukov, ebiederm, jpoimboe,
linux-kernel, mhocko, mingo, syzkaller-bugs, vegard.nossum
On Sat, Dec 09, 2017 at 02:43:00AM -0800, syzbot wrote:
>
> syzbot will keep track of this bug report.
> Once a fix for this bug is merged into any tree, 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
^ permalink raw reply [flat|nested] only message in thread