From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kuni1840@gmail.com
Subject: RE: [v1] bluetooth: hci_core: Fix use-after-free in vhci_flush().
Date: Fri, 13 Jun 2025 16:34:02 -0700 (PDT) [thread overview]
Message-ID: <684cb56a.c80a0220.7fb1f.b9e7@mx.google.com> (raw)
In-Reply-To: <20250613230228.1243343-1-kuni1840@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2831 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=972027
---Test result---
Test Summary:
CheckPatch PENDING 0.28 seconds
GitLint PENDING 0.32 seconds
SubjectPrefix FAIL 0.30 seconds
BuildKernel PASS 24.78 seconds
CheckAllWarning PASS 27.17 seconds
CheckSparse WARNING 30.51 seconds
BuildKernel32 PASS 24.54 seconds
TestRunnerSetup PASS 461.88 seconds
TestRunner_l2cap-tester PASS 24.94 seconds
TestRunner_iso-tester FAIL 7.68 seconds
TestRunner_bnep-tester PASS 5.92 seconds
TestRunner_mgmt-tester PASS 131.78 seconds
TestRunner_rfcomm-tester PASS 9.27 seconds
TestRunner_sco-tester PASS 14.67 seconds
TestRunner_ioctl-tester PASS 11.73 seconds
TestRunner_mesh-tester FAIL 7.37 seconds
TestRunner_smp-tester PASS 8.45 seconds
TestRunner_userchan-tester PASS 6.08 seconds
IncrementalBuild PENDING 0.78 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_core.c:85:9: warning: context imbalance in '__hci_dev_get' - different lock contexts for basic blocknet/bluetooth/hci_core.c: note: in included file (through include/linux/notifier.h, include/linux/memory_hotplug.h, include/linux/mmzone.h, include/linux/gfp.h, include/linux/xarray.h, include/linux/radix-tree.h, ...):
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
BUG: KASAN: slab-use-after-free in run_timer_softirq+0x76b/0x7d0
WARNING: CPU: 0 PID: 68 at kernel/workqueue.c:2257 __queue_work+0x93e/0xba0
Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Failed 0.148 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-06-13 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 23:02 [PATCH v1] bluetooth: hci_core: Fix use-after-free in vhci_flush() Kuniyuki Iwashima
2025-06-13 23:34 ` bluez.test.bot [this message]
2025-06-14 2:20 ` [v1] " Kuniyuki Iwashima
2025-06-14 11:30 ` Pauli Virtanen
2025-06-15 0:26 ` Kuniyuki Iwashima
2025-06-14 5:38 ` [PATCH v1] " Paul Menzel
2025-06-15 0:01 ` Kuniyuki Iwashima
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=684cb56a.c80a0220.7fb1f.b9e7@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kuni1840@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