From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, imv4bel@gmail.com
Subject: RE: Bluetooth: SCO: Fix use-after-free in sco_conn_ready() due to missing sock_hold
Date: Thu, 19 Mar 2026 09:37:33 -0700 (PDT) [thread overview]
Message-ID: <69bc264d.050a0220.228f92.e8bc@mx.google.com> (raw)
In-Reply-To: <abwSbezp8_z0K_eY@v4bel>
[-- Attachment #1: Type: text/plain, Size: 3440 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1069343
---Test result---
Test Summary:
CheckPatch PENDING 0.45 seconds
GitLint PENDING 0.26 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 26.66 seconds
CheckAllWarning PASS 29.30 seconds
CheckSparse PASS 28.05 seconds
BuildKernel32 PASS 25.49 seconds
TestRunnerSetup PASS 576.43 seconds
TestRunner_l2cap-tester FAIL 29.41 seconds
TestRunner_iso-tester FAIL 35.97 seconds
TestRunner_bnep-tester PASS 6.38 seconds
TestRunner_mgmt-tester FAIL 115.59 seconds
TestRunner_rfcomm-tester PASS 9.66 seconds
TestRunner_sco-tester FAIL 14.31 seconds
TestRunner_ioctl-tester PASS 10.16 seconds
TestRunner_mesh-tester FAIL 12.55 seconds
TestRunner_smp-tester FAIL 11.03 seconds
TestRunner_userchan-tester PASS 6.69 seconds
IncrementalBuild PENDING 0.55 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Total: 96, Passed: 94 (97.9%), Failed: 2, Not Run: 0
Failed Test Cases
L2CAP BR/EDR Server - Set PHY 1M Failed 0.123 seconds
L2CAP BR/EDR Server - Set PHY 2M Failed 0.122 seconds
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
BUG: KASAN: slab-use-after-free in le_read_features_complete+0x7e/0x2b0
Total: 141, Passed: 141 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.106 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 2.738 seconds
Mesh - Send cancel - 2 Timed out 1.999 seconds
##############################
Test: TestRunner_smp-tester - FAIL
Desc: Run smp-tester with test-runner
Output:
WARNING: net/bluetooth/hci_conn.c:567 at hci_conn_timeout+0x15a/0x190, CPU#0: kworker/u5:2/54
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-03-19 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 15:12 [PATCH] Bluetooth: SCO: Fix use-after-free in sco_conn_ready() due to missing sock_hold Hyunwoo Kim
2026-03-19 16:37 ` bluez.test.bot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69bc264d.050a0220.228f92.e8bc@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=imv4bel@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox