From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mhal@rbox.co
Subject: RE: net: Fix some callers of copy_from_sockptr()
Date: Thu, 14 Nov 2024 17:20:05 -0800 (PST) [thread overview]
Message-ID: <6736a1c5.050a0220.236997.4c97@mx.google.com> (raw)
In-Reply-To: <20241115-sockptr-copy-fixes-v1-1-d183c87fcbd5@rbox.co>
[-- Attachment #1: Type: text/plain, Size: 2560 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=909786
---Test result---
Test Summary:
CheckPatch PENDING 0.24 seconds
GitLint PENDING 0.20 seconds
SubjectPrefix FAIL 1.33 seconds
BuildKernel PASS 24.84 seconds
CheckAllWarning PASS 27.20 seconds
CheckSparse WARNING 30.92 seconds
BuildKernel32 PASS 24.40 seconds
TestRunnerSetup PASS 435.43 seconds
TestRunner_l2cap-tester PASS 23.36 seconds
TestRunner_iso-tester FAIL 34.58 seconds
TestRunner_bnep-tester PASS 4.81 seconds
TestRunner_mgmt-tester PASS 120.44 seconds
TestRunner_rfcomm-tester PASS 7.62 seconds
TestRunner_sco-tester PASS 11.39 seconds
TestRunner_ioctl-tester PASS 8.05 seconds
TestRunner_mesh-tester PASS 6.01 seconds
TestRunner_smp-tester PASS 7.97 seconds
TestRunner_userchan-tester PASS 5.02 seconds
IncrementalBuild PENDING 0.47 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
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
##############################
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:147:35: warning: array of flexible structures
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
Total: 124, Passed: 119 (96.0%), Failed: 1, Not Run: 4
Failed Test Cases
ISO Connect2 Suspend - Success Failed 4.238 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-11-15 1:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 23:27 [PATCH net 0/4] net: Fix some callers of copy_from_sockptr() Michal Luczaj
2024-11-14 23:27 ` [PATCH net 1/4] bluetooth: Improve setsockopt() handling of malformed user input Michal Luczaj
2024-11-15 0:42 ` David Wei
2024-11-15 2:15 ` Luiz Augusto von Dentz
2024-11-15 2:30 ` David Wei
2024-11-15 2:50 ` Luiz Augusto von Dentz
2024-11-15 3:04 ` David Wei
2024-11-15 8:31 ` Michal Luczaj
2024-11-16 0:23 ` David Wei
2024-11-15 1:20 ` bluez.test.bot [this message]
2024-11-15 2:18 ` Luiz Augusto von Dentz
2024-11-14 23:27 ` [PATCH net 2/4] llc: " Michal Luczaj
2024-11-15 13:31 ` Michal Luczaj
2024-11-14 23:27 ` [PATCH net 3/4] rxrpc: " Michal Luczaj
2024-11-14 23:27 ` [PATCH net 4/4] net: Comment copy_from_sockptr() explaining its behaviour Michal Luczaj
2024-11-15 2:43 ` David Wei
-- strict thread matches above, loose matches on Subject: below --
2024-11-15 13:21 [PATCH net v2 1/4] Bluetooth: Improve setsockopt() handling of malformed user input Michal Luczaj
2024-11-15 13:46 ` net: Fix some callers of copy_from_sockptr() bluez.test.bot
2024-11-19 13:31 [PATCH net v3 1/4] Bluetooth: Improve setsockopt() handling of malformed user input Michal Luczaj
2024-11-19 13:51 ` net: Fix some callers of copy_from_sockptr() 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=6736a1c5.050a0220.236997.4c97@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mhal@rbox.co \
/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).