From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 807DCC433DB for ; Thu, 21 Jan 2021 08:23:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 30941239CF for ; Thu, 21 Jan 2021 08:23:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727753AbhAUIWa (ORCPT ); Thu, 21 Jan 2021 03:22:30 -0500 Received: from mail.kernel.org ([198.145.29.99]:52194 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726777AbhAUISL (ORCPT ); Thu, 21 Jan 2021 03:18:11 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 3CFF42395B; Thu, 21 Jan 2021 08:17:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1611217050; bh=rEhg2xjjN69IpbKMiBBQZQFOjm8uBG9MQ7u8pZTOCKo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mOHq3m0u1pYrdCTZhc7zCLIOUIUr+IdnICQnRC+MzBgfP6tooguQ4muSBJnjAm0C4 JY2SDEdFp7Ye43KKA54bTGz1Ow9LKYoE0Y09B0NrnOsV3EUP2zPqochrbDGCKN8K6q 15/CECQcnjATULZao2ao3ao8EeFTzhHMR7CbfaMQ= Date: Thu, 21 Jan 2021 09:17:27 +0100 From: Greg KH To: =?utf-8?B?5oWV5Yas5Lqu?= Cc: jirislaby@kernel.org, linux-kernel , syzkaller-bugs , syzkaller Subject: Re: "possible deadlock in console_lock_spinning_enable" and "possible deadlock in console_unlock" should be duplicate crash behaviors Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 21, 2021 at 01:37:05PM +0800, 慕冬亮 wrote: > Dear kernel developers, > > I found that on the syzbot dashboard, “possible deadlock in > console_lock_spinning_enable”[1] and "possible deadlock in > console_unlock"[2] should share the same root cause. > > The reasons for the above statement: > 1) the stack trace is the same, and this title difference is due to > the inline property of "console_lock_spinning_enable"; > 2) their PoCs are the same as each other; > > If you can have any issues with this statement or our information is > useful to you, please let us know. Thanks very much. > > [1] “possible deadlock in console_lock_spinning_enable” - > https://syzkaller.appspot.com/bug?id=2820deb61d92a8d7ab17a56ced58e963e65d76d0 > [2] “possible deadlock in console_unlock” - > https://syzkaller.appspot.com/bug?id=39ea6caa479af471183997376dc7e90bc7d64a6a Any proposed patch for these issues? thanks, greg k-h