From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-il1-f200.google.com (mail-il1-f200.google.com [209.85.166.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C633D51026 for ; Mon, 25 Dec 2023 11:40:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-il1-f200.google.com with SMTP id e9e14a558f8ab-35fc6976630so43013365ab.0 for ; Mon, 25 Dec 2023 03:40:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703504404; x=1704109204; 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=71kCgbM33utaKn5BMCDrTj5PJAG7kVfOyQV51IZQKBQ=; b=fOe3k2McjH2xK4O+33T4sx5en3DKnws0VzKnjk6C44A35SAim4YLgdojVzd9BfybV+ koLTh1U+TWFvNvWI4zVss7/s+blqjG6F4p+9a9yp0gGJ06biD8kIFHaDMGgBHY1uLnNC PCEg4RqzfQLNPuHSsjd2Hbfar7xWglZAPK83ru4lVtKZNnfzuanMQQZmwu6HKv1bKojb DCwpBu83O+dMygMHMf5Xa6OqeDjx4DY/Ht/7kop8YFZVCDM0KabZTZxI26k/pF+p4CoV DpGreznGrJoVqNqAG97k3aZAIeNP2VyV6cNv91CkhTh5daK/hGxZ2xtmnzyV006Bm/fQ 7/9A== X-Gm-Message-State: AOJu0YznNsGQDx4WKn3sPr7KidB95tWe5YlGKhn5OjSMmtDGkDFhOu/J JYXiGlGJozRN47810BObU4xh817+tktbZIDJ/Ags9shjfIm+ X-Google-Smtp-Source: AGHT+IFhxcJ9tk5FyfUnUpIIbakXuToDfa46uJd5K9yO2+cEAsusUl61NtfW50SDPW/cdQOaoTXt432KoUncWYcBxMOHU8A65NXf Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6e02:148d:b0:360:fa:2c2c with SMTP id n13-20020a056e02148d00b0036000fa2c2cmr126623ilk.6.1703504404109; Mon, 25 Dec 2023 03:40:04 -0800 (PST) Date: Mon, 25 Dec 2023 03:40:04 -0800 In-Reply-To: <0000000000004c51dd0605109d19@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000e16572060d5406f8@google.com> Subject: Re: [syzbot] [bluetooth?] general protection fault in lock_sock_nested 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, pav@iki.fi, syzkaller-bugs@googlegroups.com, william.xuanziyang@huawei.com Content-Type: text/plain; charset="UTF-8" syzbot suspects this issue was fixed by commit: commit 181a42edddf51d5d9697ecdf365d72ebeab5afb0 Author: Ziyang Xuan Date: Wed Oct 11 09:57:31 2023 +0000 Bluetooth: Make handle of hci_conn be unique bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15f7f6cee80000 start commit: ae074e2b2fd4 sfc: check for zero length in EF10 RX prefix git tree: net kernel config: https://syzkaller.appspot.com/x/.config?x=634e05b4025da9da dashboard link: https://syzkaller.appspot.com/bug?extid=d3ccfb78a0dc16ffebe3 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13075977a80000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1012d447a80000 If the result looks correct, please mark the issue as fixed by replying with: #syz fix: Bluetooth: Make handle of hci_conn be unique For information about bisection process see: https://goo.gl/tpsmEJ#bisection