From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, eadavis@qq.com
Subject: RE: bluetooth: handle value within the ida range should not be handled in BIG
Date: Sun, 16 Jun 2024 03:59:05 -0700 (PDT) [thread overview]
Message-ID: <666ec579.050a0220.39ff8.d4a2@mx.google.com> (raw)
In-Reply-To: <tencent_880C74B1776566183DC9363096E037A64A09@qq.com>
[-- Attachment #1: Type: text/plain, Size: 4976 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=862356
---Test result---
Test Summary:
CheckPatch FAIL 0.86 seconds
GitLint FAIL 0.47 seconds
SubjectPrefix FAIL 0.28 seconds
BuildKernel PASS 29.86 seconds
CheckAllWarning PASS 33.44 seconds
CheckSparse WARNING 38.13 seconds
CheckSmatch WARNING 102.54 seconds
BuildKernel32 PASS 29.65 seconds
TestRunnerSetup PASS 527.95 seconds
TestRunner_l2cap-tester PASS 18.19 seconds
TestRunner_iso-tester PASS 32.28 seconds
TestRunner_bnep-tester PASS 4.81 seconds
TestRunner_mgmt-tester FAIL 110.14 seconds
TestRunner_rfcomm-tester PASS 7.36 seconds
TestRunner_sco-tester PASS 15.04 seconds
TestRunner_ioctl-tester PASS 10.65 seconds
TestRunner_mesh-tester PASS 7.88 seconds
TestRunner_smp-tester PASS 6.80 seconds
TestRunner_userchan-tester PASS 4.96 seconds
IncrementalBuild PASS 27.95 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
bluetooth: handle value within the ida range should not be handled in BIG
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#89:
hci_le_big_sync_established_evt is necessary to filter out cases where the handle
WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#94:
Reported-by: syzbot+b2545b087a01a7319474@syzkaller.appspotmail.com
Signed-off-by: Edward Adam Davis <eadavis@qq.com>
ERROR: code indent should use tabs where possible
#108: FILE: net/bluetooth/hci_event.c:6896:
+ if (handle > HCI_CONN_HANDLE_MAX)$
WARNING: please, no spaces at the start of a line
#108: FILE: net/bluetooth/hci_event.c:6896:
+ if (handle > HCI_CONN_HANDLE_MAX)$
WARNING: suspect code indent for conditional statements (24, 31)
#108: FILE: net/bluetooth/hci_event.c:6896:
+ if (handle > HCI_CONN_HANDLE_MAX)
+ continue;
ERROR: code indent should use tabs where possible
#109: FILE: net/bluetooth/hci_event.c:6897:
+ continue;$
WARNING: please, no spaces at the start of a line
#109: FILE: net/bluetooth/hci_event.c:6897:
+ continue;$
total: 2 errors, 5 warnings, 0 checks, 9 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
NOTE: Whitespace errors detected.
You may wish to use scripts/cleanpatch or scripts/cleanfile
/github/workspace/src/src/13699512.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
bluetooth: handle value within the ida range should not be handled in BIG
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
3: B1 Line exceeds max length (81>80): "hci_le_big_sync_established_evt is necessary to filter out cases where the handle"
4: B2 Line has trailing whitespace: "value is belone to ida id range, otherwise ida will be erroneously released in "
5: B2 Line has trailing whitespace: "hci_conn_cleanup. "
##############################
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_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 7 (AL is full) Failed 0.190 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-06-16 10:59 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 ` bluez.test.bot [this message]
2024-06-16 13:21 ` [PATCH] Bluetooth: handle value is too large should not be used in BIG Edward Adam Davis
2024-06-16 14:33 ` bluez.test.bot
2024-06-16 20:44 ` [PATCH] " 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=666ec579.050a0220.39ff8.d4a2@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.