From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, security@1seal.org
Subject: RE: Bluetooth: SMP: honor local MITM requirements for legacy pairing
Date: Mon, 30 Mar 2026 09:25:15 -0700 (PDT) [thread overview]
Message-ID: <69caa3eb.050a0220.17a49.fd54@mx.google.com> (raw)
In-Reply-To: <78570f37f1da48f38336480ba61e29d9.security@1seal.org>
[-- Attachment #1: Type: text/plain, Size: 2913 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=1074695
---Test result---
Test Summary:
CheckPatch PENDING 0.72 seconds
GitLint PENDING 0.41 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 26.81 seconds
CheckAllWarning PASS 29.79 seconds
CheckSparse PASS 28.09 seconds
BuildKernel32 PASS 25.94 seconds
TestRunnerSetup PASS 567.37 seconds
TestRunner_l2cap-tester PASS 29.34 seconds
TestRunner_iso-tester PASS 39.60 seconds
TestRunner_bnep-tester PASS 6.23 seconds
TestRunner_mgmt-tester FAIL 112.23 seconds
TestRunner_rfcomm-tester PASS 9.38 seconds
TestRunner_sco-tester FAIL 14.27 seconds
TestRunner_ioctl-tester PASS 9.93 seconds
TestRunner_mesh-tester FAIL 11.47 seconds
TestRunner_smp-tester PASS 10.45 seconds
TestRunner_userchan-tester PASS 6.60 seconds
IncrementalBuild PENDING 0.60 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: 494, Passed: 485 (98.2%), Failed: 5, Not Run: 4
Failed Test Cases
Adv. connectable & connected (central) - Success Failed 0.125 seconds
Adv. non-connectable & connected (central) - Success Failed 0.122 seconds
Ext Adv. connectable & connected (central) Failed 0.182 seconds
Ext Adv. non-connectable & connected (central) Failed 0.185 seconds
Read Exp Feature - Success Failed 0.108 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 1.837 seconds
Mesh - Send cancel - 2 Timed out 1.993 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-03-30 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 15:33 [PATCH v3 0/2] Bluetooth: SMP: honor local MITM requirements for legacy pairing Oleh Konko
2026-03-30 15:33 ` [PATCH v3 1/2] Bluetooth: SMP: honor local HIGH security when selecting legacy pairing method Oleh Konko
2026-03-30 16:25 ` bluez.test.bot [this message]
2026-03-30 16:27 ` Luiz Augusto von Dentz
2026-03-30 19:36 ` Luiz Augusto von Dentz
2026-03-30 15:33 ` [PATCH v3 2/2] Bluetooth: SMP: derive legacy responder STK authentication from MITM state Oleh Konko
-- strict thread matches above, loose matches on Subject: below --
2026-03-31 11:52 [PATCH v4 1/2] Bluetooth: SMP: force responder MITM requirements before building the pairing response Oleh Konko
2026-03-31 13:25 ` Bluetooth: SMP: honor local MITM requirements for legacy pairing 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=69caa3eb.050a0220.17a49.fd54@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=security@1seal.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox