From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, eadavis@qq.com
Subject: RE: Bluetooth: handle value is too large should not be used in BIG
Date: Sun, 16 Jun 2024 07:33:20 -0700 (PDT) [thread overview]
Message-ID: <666ef7b0.170a0220.1856.4644@mx.google.com> (raw)
In-Reply-To: <tencent_410DFAA59E0DBA9213DDE8DD9399584FDB07@qq.com>
[-- Attachment #1: Type: text/plain, Size: 2093 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=862371
---Test result---
Test Summary:
CheckPatch PASS 0.47 seconds
GitLint PASS 0.19 seconds
SubjectPrefix PASS 0.05 seconds
BuildKernel PASS 30.65 seconds
CheckAllWarning PASS 33.08 seconds
CheckSparse WARNING 38.43 seconds
CheckSmatch WARNING 103.85 seconds
BuildKernel32 PASS 29.56 seconds
TestRunnerSetup PASS 533.58 seconds
TestRunner_l2cap-tester PASS 18.51 seconds
TestRunner_iso-tester PASS 37.01 seconds
TestRunner_bnep-tester PASS 4.80 seconds
TestRunner_mgmt-tester FAIL 113.65 seconds
TestRunner_rfcomm-tester PASS 7.67 seconds
TestRunner_sco-tester PASS 17.04 seconds
TestRunner_ioctl-tester PASS 7.94 seconds
TestRunner_mesh-tester PASS 5.89 seconds
TestRunner_smp-tester PASS 6.91 seconds
TestRunner_userchan-tester PASS 5.06 seconds
IncrementalBuild PASS 28.50 seconds
Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 492, Passed: 489 (99.4%), Failed: 1, Not Run: 2
Failed Test Cases
LL Privacy - Add Device 5 (2 Devices to RL) Failed 0.174 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-06-16 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 4:53 [syzbot] [bluetooth?] WARNING in hci_conn_del syzbot
2024-06-13 21:15 ` [syzbot] " syzbot
2024-06-16 10:14 ` [syzbot] [bluetooth?] " Edward Adam Davis
2024-06-16 10:33 ` syzbot
2024-06-16 10:20 ` [PATCH] bluetooth: handle value within the ida range should not be handled in BIG Edward Adam Davis
2024-06-16 10:37 ` Pavel Skripkin
2024-06-16 13:18 ` [syzbot] [bluetooth?] WARNING in hci_conn_del Edward Adam Davis
2024-06-16 10:59 ` bluetooth: handle value within the ida range should not be handled in BIG bluez.test.bot
2024-06-16 13:21 ` [PATCH] Bluetooth: handle value is too large should not be used " Edward Adam Davis
2024-06-16 14:33 ` bluez.test.bot [this message]
2024-06-16 20:44 ` Paul Menzel
2024-06-17 11:09 ` [PATCH v2] Bluetooth: Ignore too large handle values " Edward Adam Davis
2024-06-17 11:57 ` [v2] " bluez.test.bot
2024-06-17 14:10 ` [PATCH v2] " patchwork-bot+bluetooth
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=666ef7b0.170a0220.1856.4644@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=eadavis@qq.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.