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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0D173C636D7 for ; Thu, 2 Feb 2023 04:55:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230375AbjBBEzd (ORCPT ); Wed, 1 Feb 2023 23:55:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43486 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230048AbjBBEzc (ORCPT ); Wed, 1 Feb 2023 23:55:32 -0500 Received: from mail-io1-f71.google.com (mail-io1-f71.google.com [209.85.166.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6E81762780 for ; Wed, 1 Feb 2023 20:55:29 -0800 (PST) Received: by mail-io1-f71.google.com with SMTP id d24-20020a5d9bd8000000b006ee2ddf6d77so545166ion.6 for ; Wed, 01 Feb 2023 20:55:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=xCXSBKHFGkOitij945KHNCtiG7h7wsgd2ox/b52l/XU=; b=kWRCrcIAoK5rv568xYbAMLgeR/S8RjICGHe3QRe9vcoTXZFsxFa6Le8LTD6Jhp8FHL 5OWf+qSaJ67Ly1vucC55x0G0Azdel7boGNZSTrnCU3Og16zGZ/8F9q37s9IeocfQu12M BysX212OayP6Xf2rfQ3xNPiZSz2b8FxTJxcRPdbjwB42W2aFXuaHJQJLrV7eTP22IJiW s7gjclb7o/7M/6mzyM62iWTt+F+GIol3IRCqiLy4FUu15iLLhtusSnQ8X0maVBqQ2quq k2CwFBFukVk+QyqyL6KmKFx4sOaiivvzNUNEqhToShVQpv5XL+7UvZ1cYThzMNFPT7O1 fiwQ== X-Gm-Message-State: AO0yUKUnEjsHgUyoZZ+1yhgpjFL9V/RHVcw6tY0yNRY8sPZEv2wxE7vl KfC3i+6ybOhKo4Zo36PndfrYBprMjAZ3aPEQheYqZ+PmOgrz X-Google-Smtp-Source: AK7set+N2Jjm/A0Fcquix/C4kGyTpSc3SJa3KNEpZGWx5tPfcEn1CG5T8fQ71o0Ao+DdWsZSutWOpYedoho79O8kyl9cOTdEQUKN MIME-Version: 1.0 X-Received: by 2002:a92:b302:0:b0:310:c8e5:a1a6 with SMTP id p2-20020a92b302000000b00310c8e5a1a6mr1184080ilh.129.1675313728754; Wed, 01 Feb 2023 20:55:28 -0800 (PST) Date: Wed, 01 Feb 2023 20:55:28 -0800 In-Reply-To: <0000000000005e857005db658b71@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000b09dc705f3b05f9b@google.com> Subject: Re: [syzbot] INFO: task hung in rfcomm_process_sessions (2) From: syzbot To: davem@davemloft.net, edumazet@google.com, hdanton@sina.com, johan.hedberg@gmail.com, kuba@kernel.org, linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, luiz.dentz@gmail.com, luiz.von.dentz@intel.com, marcel@holtmann.org, netdev@vger.kernel.org, pabeni@redhat.com, syzkaller-bugs@googlegroups.com, yinghsu@chromium.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org syzbot suspects this issue was fixed by commit: commit 1d80d57ffcb55488f0ec0b77928d4f82d16b6a90 Author: Ying Hsu Date: Wed Jan 11 03:16:14 2023 +0000 Bluetooth: Fix possible deadlock in rfcomm_sk_state_change bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=154b77b5480000 start commit: d888c83fcec7 fs: fix fd table size alignment properly git tree: upstream kernel config: https://syzkaller.appspot.com/x/.config?x=69c8957f4ac2dea6 dashboard link: https://syzkaller.appspot.com/bug?extid=d761775dff24be3ad4be syz repro: https://syzkaller.appspot.com/x/repro.syz?x=162ca1fd700000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1036182d700000 If the result looks correct, please mark the issue as fixed by replying with: #syz fix: Bluetooth: Fix possible deadlock in rfcomm_sk_state_change For information about bisection process see: https://goo.gl/tpsmEJ#bisection