From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f181.google.com ([209.85.223.181]:41870 "EHLO mail-io0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752415AbdLLVZF (ORCPT ); Tue, 12 Dec 2017 16:25:05 -0500 Date: Tue, 12 Dec 2017 13:25:01 -0800 From: Eric Biggers To: syzbot Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk Subject: Re: possible deadlock in fifo_open Message-ID: <20171212212501.GE185376@gmail.com> References: <001a11440c804d07b4055f46d902@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001a11440c804d07b4055f46d902@google.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Dec 01, 2017 at 04:53: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