From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f199.google.com (mail-oi1-f199.google.com [209.85.167.199]) (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 4C43E372B3C for ; Sat, 21 Mar 2026 11:28:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.199 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774092502; cv=none; b=grj5KHQ2ThkKYs9bqPWKCAfbA+yzQGRqXcC06SqMzdljkYSoRyo/4AZ97tfCVfRL+Ni0rnmuf86b+sGP94AP+oSIFBB1VIFyeQqAJxvdL7+sBYkLmKc52IrUZIK5YDEAczVtM2zytwreKJE5t46TWBP3OeD2BUMJgVRzamuY1mk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774092502; c=relaxed/simple; bh=wI2k9Tz2JD+U6tZ/jMbAcUaoook+uA2cGSQ7KGaGfic=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=AKmWJQpKL6uHEvaPMh0zxXlXddMVSy4qET5gl+HE/iBQyuZI5BlfAj2cQ7qYenqJ35q9Nrx1jd8KQRgJd2K9fPFNPJRyuXok/2/fX6CpUIJqaaWnETx386XuONhnMfwqcic6Tdk34h2rwa50oXHQjOAF4ug9DZ6YUCswnOynqx8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.167.199 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-oi1-f199.google.com with SMTP id 5614622812f47-467e8aaa943so5048821b6e.0 for ; Sat, 21 Mar 2026 04:28:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1774092499; x=1774697299; 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=4pT5gyLRM0wYaOahTlGtvZ/5cOONF8GgMaw4h5anmK4=; b=ZJKTEmQMG5OcW1G0d4cxUdUZwJfC8TS+c3k+OhNDBF6TLmBkVXZGrrlu8XcO7SzjFP hIl3ktQzgafLfLDYmNqzBXnQewssKZFi1rLdTU2VS6Ks0RARm800SsWltVfyv2AlP6ou 5W8Ujl3bfIMJht1j/PIjswoBXHIo3ekfFlcM7Nr6vlvV5ldOLBpn/zjUnDX/RLDLlhjJ KZSdIvAWkYBaFKCY1rHvUV0r2sSQOXFiFgIYlSj9jVXWVcpfFFY4B9g/fCLP+mWJ3Uk3 JZdJQ7qYBE1aVrPLL2I6lUHUMuRV8fj7QCvo8dubAARhQ8FTmh+EINkhkCQ7c9gSZonC KCNg== X-Gm-Message-State: AOJu0YzAWfGmM2IOaG3sN2b5jA7ciLUXZAigv2LPCMxa8nBZ7TPnxQqk EitzY/6ZuDk46j2o4SKGZpN3opyEVQzfEGJYdSFF08EQXJ4S83J0TAjRL9O57jpS5Yoe32jMZcx wXhy4NXyz4J2DYDcfxrgzo2nvfnEBOq3aHlLE3NLBbR2bu4Crj9jNW3vCmYE= 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:6808:10c9:b0:450:bb4e:8395 with SMTP id 5614622812f47-467e5fcc274mr3107352b6e.53.1774092499171; Sat, 21 Mar 2026 04:28:19 -0700 (PDT) Date: Sat, 21 Mar 2026 04:28:19 -0700 In-Reply-To: <000000000000cd69c7061dfe35d2@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69be80d3.050a0220.3bf4de.004d.GAE@google.com> Subject: Forwarded: test fix for syzbot+b170dbf55520ebf5969a From: syzbot To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com. *** Subject: test fix for syzbot+b170dbf55520ebf5969a Author: abysamross@gmail.com #syz test =============================== >From 4c574f30487b7aa767f29689692e1e54d672c508 Mon Sep 17 00:00:00 2001 From: Aby Sam Ross Date: Sat, 21 Mar 2026 15:12:16 +0530 Subject: [PATCH v1 1/1] Bluetooth: hci_release_dev: disable delayed hci devcoredump timeout work It is not necessary that the pending delayed hci devcoredump timeout work, hdev->dump.dump_timeout, submitted to the hdev->workqueue by the bluetooth devcoredump state machine, hci_devcd_rx() ( --> hci_devcd_handle_pkt_init()) will be reset by it or by the timeout func hci_devcd_timeout() before destroying the workqueue or before the hci device is freed up in hci_release_dev(). In this bug the active delayed devcoredump timeout work's timer object is active when the memory associated with the hci device is freed up in hci_release_dev() causing the ODEBUG WARNING. Make sure that the delayed devcoredump timeout work is disabled before the hdev->workqueue is destroyed and before the hdev memory is freed in hci_release_dev(). Tested the change with the syzbot reproducer that uses a vhci device locally on x86_64 and on syzbot portal as well. Closes: https://syzkaller.appspot.com/bug?extid=b170dbf55520ebf5969a Tested-by: syzbot+b170dbf55520ebf5969a@syzkaller.appspotmail.com Reported-by: syzbot+b170dbf55520ebf5969a@syzkaller.appspotmail.com Signed-off-by: Aby Sam Ross --- net/bluetooth/hci_core.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/net/bluetooth/hci_core.c b/net/bluetooth/hci_core.c index 31308c1de4ec..3e7b4c8576b2 100644 --- a/net/bluetooth/hci_core.c +++ b/net/bluetooth/hci_core.c @@ -2747,6 +2747,9 @@ void hci_release_dev(struct hci_dev *hdev) kfree_const(hdev->hw_info); kfree_const(hdev->fw_info); + if (hdev->dump.supported) { + disable_delayed_work_sync(&hdev->dump.dump_timeout); + } destroy_workqueue(hdev->workqueue); destroy_workqueue(hdev->req_workqueue); -- 2.53.0