From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: Bluetooth: Fix double free in hci_conn_cleanup
Date: Thu, 30 Mar 2023 15:32:22 -0700 (PDT) [thread overview]
Message-ID: <64260df6.050a0220.1b610.173b@mx.google.com> (raw)
In-Reply-To: <20230330220332.1035910-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3071 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=735599
---Test result---
Test Summary:
CheckPatch PASS 1.52 seconds
GitLint FAIL 0.92 seconds
SubjectPrefix PASS 0.25 seconds
BuildKernel PASS 31.54 seconds
CheckAllWarning PASS 34.24 seconds
CheckSparse WARNING 38.81 seconds
CheckSmatch WARNING 108.45 seconds
BuildKernel32 PASS 30.22 seconds
TestRunnerSetup PASS 432.40 seconds
TestRunner_l2cap-tester PASS 15.85 seconds
TestRunner_iso-tester PASS 15.51 seconds
TestRunner_bnep-tester PASS 5.08 seconds
TestRunner_mgmt-tester PASS 107.05 seconds
TestRunner_rfcomm-tester PASS 8.07 seconds
TestRunner_sco-tester PASS 7.52 seconds
TestRunner_ioctl-tester PASS 8.65 seconds
TestRunner_mesh-tester PASS 6.45 seconds
TestRunner_smp-tester PASS 7.39 seconds
TestRunner_userchan-tester PASS 5.30 seconds
IncrementalBuild PASS 33.27 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: Fix double free in hci_conn_cleanup
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
34: B1 Line exceeds max length (87>80): "Link: https://syzkaller.appspot.com/bug?id=1bb51491ca5df96a5f724899d1dbb87afda61419 [1]"
[2/2] Bluetooth: SCO: Fix possible circular locking dependency sco_sock_getsockopt
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
1: T1 Title exceeds max length (82>80): "[2/2] Bluetooth: SCO: Fix possible circular locking dependency sco_sock_getsockopt"
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:149:35: warning: array of flexible structures
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:149:35: warning: array of flexible structures
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-03-30 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 22:03 [PATCH] Bluetooth: Fix double free in hci_conn_cleanup Luiz Augusto von Dentz
2023-03-30 22:03 ` [PATCH 1/2] Bluetooth: SCO: Fix possible circular locking dependency on sco_connect_cfm Luiz Augusto von Dentz
2023-03-30 22:35 ` [1/2] " bluez.test.bot
2023-03-31 22:10 ` [PATCH 1/2] " patchwork-bot+bluetooth
2023-03-30 22:03 ` [PATCH 2/2] Bluetooth: SCO: Fix possible circular locking dependency sco_sock_getsockopt Luiz Augusto von Dentz
2023-03-30 22:32 ` bluez.test.bot [this message]
2023-03-31 22:10 ` [PATCH] Bluetooth: Fix double free in hci_conn_cleanup patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-03-30 22:02 Luiz Augusto von Dentz
2023-03-30 22:32 ` bluez.test.bot
2023-03-09 9:34 [PATCH] " ZhengHan Wang
2023-03-09 10:02 ` bluez.test.bot
2023-03-09 7:46 [PATCH] " ZhengHan Wang
2023-03-09 8:43 ` bluez.test.bot
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=64260df6.050a0220.1b610.173b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).