From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752697AbdLLV7a (ORCPT ); Tue, 12 Dec 2017 16:59:30 -0500 Received: from mail-io0-f170.google.com ([209.85.223.170]:40502 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752564AbdLLV7Z (ORCPT ); Tue, 12 Dec 2017 16:59:25 -0500 X-Google-Smtp-Source: ACJfBouwp7PYY62kqP9hjCyfEIInQJv9+c/fvzkJseIlv1YE9/xZVvLdmhshwDBDFBTStJPUsNm5bQ== Date: Tue, 12 Dec 2017 13:59:20 -0800 From: Eric Biggers To: syzbot Cc: adobriyan@gmail.com, akinobu.mita@gmail.com, akpm@linux-foundation.org, dvyukov@google.com, ebiederm@xmission.com, jani.nikula@intel.com, linux-kernel@vger.kernel.org, mingo@kernel.org, syzkaller-bugs@googlegroups.com, vegard.nossum@oracle.com Subject: Re: possible deadlock in lock_trace Message-ID: <20171212215920.GH185376@gmail.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 30, 2017 at 10:39:02AM -0800, syzbot wrote: > This bug is generated by a dumb bot. It may contain errors. > See https://goo.gl/tpsmEJ for details. > Direct all questions to syzkaller@googlegroups.com. > Please credit me with: Reported-by: syzbot > > 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