From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v5] Bluetooth: L2CAP: Fix slab-use-after-free Read in l2cap_send_cmd
Date: Wed, 22 Jan 2025 11:54:22 -0800 (PST) [thread overview]
Message-ID: <67914cee.050a0220.1ae01f.b4e1@mx.google.com> (raw)
In-Reply-To: <20250122192016.86251-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1948 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=927638
---Test result---
Test Summary:
CheckPatch PENDING 0.26 seconds
GitLint PENDING 0.18 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 24.29 seconds
CheckAllWarning PASS 26.56 seconds
CheckSparse PASS 30.03 seconds
BuildKernel32 PASS 24.15 seconds
TestRunnerSetup PASS 427.69 seconds
TestRunner_l2cap-tester PASS 20.54 seconds
TestRunner_iso-tester PASS 36.85 seconds
TestRunner_bnep-tester PASS 4.83 seconds
TestRunner_mgmt-tester FAIL 124.94 seconds
TestRunner_rfcomm-tester PASS 7.59 seconds
TestRunner_sco-tester PASS 9.31 seconds
TestRunner_ioctl-tester PASS 8.06 seconds
TestRunner_mesh-tester PASS 5.89 seconds
TestRunner_smp-tester PASS 6.86 seconds
TestRunner_userchan-tester PASS 5.00 seconds
IncrementalBuild PENDING 0.66 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
LL Privacy - Set Device Flag 1 (Device Privacy) Failed 0.158 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2025-01-22 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 19:20 [PATCH v5] Bluetooth: L2CAP: Fix slab-use-after-free Read in l2cap_send_cmd Luiz Augusto von Dentz
2025-01-22 19:54 ` bluez.test.bot [this message]
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=67914cee.050a0220.1ae01f.b4e1@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 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.