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=-3.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, 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 8D7EBC433EF for ; Mon, 13 Sep 2021 05:15:26 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 2284060F9D for ; Mon, 13 Sep 2021 05:15:26 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 2284060F9D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id 399B06B0071; Mon, 13 Sep 2021 01:15:25 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 34923900002; Mon, 13 Sep 2021 01:15:25 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 25E886B0073; Mon, 13 Sep 2021 01:15:25 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0008.hostedemail.com [216.40.44.8]) by kanga.kvack.org (Postfix) with ESMTP id 17C766B0071 for ; Mon, 13 Sep 2021 01:15:25 -0400 (EDT) Received: from smtpin27.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id BA9F7181AF5CC for ; Mon, 13 Sep 2021 05:15:24 +0000 (UTC) X-FDA: 78581386968.27.C24D03D Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) by imf12.hostedemail.com (Postfix) with ESMTP id 6969010000A3 for ; Mon, 13 Sep 2021 05:15:24 +0000 (UTC) Received: by mail-io1-f70.google.com with SMTP id o128-20020a6bbe86000000b005bd06eaeca6so13057191iof.22 for ; Sun, 12 Sep 2021 22:15:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=dTVsWZPyEZSZb6YETT9aCHK9GgOqBT0Lc4pHP3Lx6e8=; b=JaYNwUzLLaWQ+PLiCh6/b9mSN2pA3mZU879R37sqUt7S2HcSNnC3gRI9E20h3+OL7j Ak+tcIfiT8QQpIGOJRJSJpRINMr0LEf74/G4gOilYYbbcLPn63Z9iOdT7eYz0PWCCDwK g8mh2NNY1sd9OTpf2LcA94tHvC5jKZhJpNGUdvsnDFj+kFUkSwOjuPokpTNnCZc8ejis hZ7TtpWlo3EFCtWy9ovUV0m9BbF3eK74eEoC1Mo1RXr2lUjovZEG5fB3SvkL6fWXDtAV K3yveEUzOt8Y7nFbbudqLkiROEElXpmwBBbTfK4ZlVmYN/Mma8si68wlnPYdqwc/btAU Qkcw== X-Gm-Message-State: AOAM532HREHY0XGMTCLfDAY8CSqKNH7JTX2nu2/IShHczwOGJIrW8nOX B2qq2BoocPl6KzIAsE02/DyKElVB2MwBQvQtuexBIjK3dXPw X-Google-Smtp-Source: ABdhPJwO7iV5Xgy+j0Lqk/9D8z0ZhHnqpHxWMiJvuG9Vcu9TbDCEif0fnrEUbAbQSchI7yx4o/iva7NqZw76Vn3WUO2k9LiIPSBi MIME-Version: 1.0 X-Received: by 2002:a02:3b58:: with SMTP id i24mr8092839jaf.144.1631510123863; Sun, 12 Sep 2021 22:15:23 -0700 (PDT) Date: Sun, 12 Sep 2021 22:15:23 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000061641905cbd98d7b@google.com> Subject: [syzbot] possible deadlock in rfcomm_sk_state_change From: syzbot To: akpm@linux-foundation.org, davem@davemloft.net, desmondcheongzx@gmail.com, johan.hedberg@gmail.com, kuba@kernel.org, linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, luiz.dentz@gmail.com, marcel@holtmann.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com, tedd.an@intel.com Content-Type: text/plain; charset="UTF-8" Authentication-Results: imf12.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf12.hostedemail.com: domain of 3a94-YQkbADQiopaQbbUhQffYT.WeeWbUkiUhSedjUdj.Sec@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.70 as permitted sender) smtp.mailfrom=3a94-YQkbADQiopaQbbUhQffYT.WeeWbUkiUhSedjUdj.Sec@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com X-Rspamd-Server: rspam06 X-Rspamd-Queue-Id: 6969010000A3 X-Stat-Signature: yk3to319kb575z9t7zcug8eabfrtktrw X-HE-Tag: 1631510124-678140 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Hello, syzbot found the following issue on: HEAD commit: a3fa7a101dcf Merge branches 'akpm' and 'akpm-hotfixes' (pa.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10d61a8b300000 kernel config: https://syzkaller.appspot.com/x/.config?x=a9b60f3b657f313d dashboard link: https://syzkaller.appspot.com/bug?extid=d7ce59b06b3eb14fd218 compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.1 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15247a7d300000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12a2642b300000 The issue was bisected to: commit 1804fdf6e494e5e2938c65d8391690b59bcff897 Author: Tedd Ho-Jeong An Date: Thu Aug 5 00:32:19 2021 +0000 Bluetooth: btintel: Combine setting up MSFT extension bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=125f4163300000 final oops: https://syzkaller.appspot.com/x/report.txt?x=115f4163300000 console output: https://syzkaller.appspot.com/x/log.txt?x=165f4163300000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+d7ce59b06b3eb14fd218@syzkaller.appspotmail.com Fixes: 1804fdf6e494 ("Bluetooth: btintel: Combine setting up MSFT extension") ====================================================== WARNING: possible circular locking dependency detected 5.14.0-syzkaller #0 Not tainted ------------------------------------------------------ krfcommd/2875 is trying to acquire lock: ffff888012b9d120 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1612 [inline] ffff888012b9d120 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x63/0x300 net/bluetooth/rfcomm/sock.c:73 but task is already holding lock: ffff88807cf12528 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x281/0x480 net/bluetooth/rfcomm/core.c:487 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&d->lock){+.+.}-{3:3}: lock_acquire+0x19f/0x4d0 kernel/locking/lockdep.c:5625 __mutex_lock_common+0x1df/0x2550 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x1a/0x20 kernel/locking/mutex.c:743 __rfcomm_dlc_close+0x281/0x480 net/bluetooth/rfcomm/core.c:487 rfcomm_process_dlcs+0x92/0x620 net/bluetooth/rfcomm/core.c:1844 rfcomm_process_sessions+0x2f6/0x3f0 net/bluetooth/rfcomm/core.c:2003 rfcomm_run+0x195/0x2c0 net/bluetooth/rfcomm/core.c:2086 kthread+0x453/0x480 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 -> #1 (rfcomm_mutex){+.+.}-{3:3}: lock_acquire+0x19f/0x4d0 kernel/locking/lockdep.c:5625 __mutex_lock_common+0x1df/0x2550 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x1a/0x20 kernel/locking/mutex.c:743 rfcomm_dlc_open+0x25/0x50 net/bluetooth/rfcomm/core.c:425 rfcomm_sock_connect+0x285/0x470 net/bluetooth/rfcomm/sock.c:413 __sys_connect_file net/socket.c:1896 [inline] __sys_connect+0x38a/0x410 net/socket.c:1913 __do_sys_connect net/socket.c:1923 [inline] __se_sys_connect net/socket.c:1920 [inline] __x64_sys_connect+0x76/0x80 net/socket.c:1920 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3051 [inline] check_prevs_add kernel/locking/lockdep.c:3174 [inline] validate_chain+0x1dfb/0x8240 kernel/locking/lockdep.c:3789 __lock_acquire+0x1382/0x2b00 kernel/locking/lockdep.c:5015 lock_acquire+0x19f/0x4d0 kernel/locking/lockdep.c:5625 lock_sock_nested+0xc6/0x110 net/core/sock.c:3191 lock_sock include/net/sock.h:1612 [inline] rfcomm_sk_state_change+0x63/0x300 net/bluetooth/rfcomm/sock.c:73 __rfcomm_dlc_close+0x2cc/0x480 net/bluetooth/rfcomm/core.c:489 rfcomm_process_dlcs+0x92/0x620 net/bluetooth/rfcomm/core.c:1844 rfcomm_process_sessions+0x2f6/0x3f0 net/bluetooth/rfcomm/core.c:2003 rfcomm_run+0x195/0x2c0 net/bluetooth/rfcomm/core.c:2086 kthread+0x453/0x480 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 other info that might help us debug this: Chain exists of: sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM --> rfcomm_mutex --> &d->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&d->lock); lock(rfcomm_mutex); lock(&d->lock); lock(sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM); *** DEADLOCK *** 2 locks held by krfcommd/2875: #0: ffffffff8dac7488 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_process_sessions+0x21/0x3f0 net/bluetooth/rfcomm/core.c:1979 #1: ffff88807cf12528 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x281/0x480 net/bluetooth/rfcomm/core.c:487 stack backtrace: CPU: 1 PID: 2875 Comm: krfcommd Not tainted 5.14.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1dc/0x2d8 lib/dump_stack.c:106 check_noncircular+0x2f9/0x3b0 kernel/locking/lockdep.c:2131 check_prev_add kernel/locking/lockdep.c:3051 [inline] check_prevs_add kernel/locking/lockdep.c:3174 [inline] validate_chain+0x1dfb/0x8240 kernel/locking/lockdep.c:3789 __lock_acquire+0x1382/0x2b00 kernel/locking/lockdep.c:5015 lock_acquire+0x19f/0x4d0 kernel/locking/lockdep.c:5625 lock_sock_nested+0xc6/0x110 net/core/sock.c:3191 lock_sock include/net/sock.h:1612 [inline] rfcomm_sk_state_change+0x63/0x300 net/bluetooth/rfcomm/sock.c:73 __rfcomm_dlc_close+0x2cc/0x480 net/bluetooth/rfcomm/core.c:489 rfcomm_process_dlcs+0x92/0x620 net/bluetooth/rfcomm/core.c:1844 rfcomm_process_sessions+0x2f6/0x3f0 net/bluetooth/rfcomm/core.c:2003 rfcomm_run+0x195/0x2c0 net/bluetooth/rfcomm/core.c:2086 kthread+0x453/0x480 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches