Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mohammed.saad.alquraini@gmail.com
Subject: RE: Bluetooth: L2CAP: check security before completing a deferred BR/EDR accept
Date: Wed, 18 Nov 2026 17:07:10 -0800 (PST)	[thread overview]
Message-ID: <6afe4bbe.5da39d67.21e96f.ecd1@mx.google.com> (raw)
In-Reply-To: <20261118213322.60067-1-mohammed.saad.alquraini@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3898 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/series/1215445/

---Test result---

Test Summary:
CheckPatch                    FAIL      1.26 seconds
VerifyFixes                   PASS      0.13 seconds
VerifySignedoff               PASS      0.13 seconds
GitLint                       PASS      0.34 seconds
SubjectPrefix                 PASS      0.12 seconds
BuildKernel                   PASS      30.69 seconds
CheckAllWarning               PASS      35.07 seconds
CheckSparse                   PASS      37.80 seconds
BuildKernel32                 PASS      31.01 seconds
CheckKernelLLVM               FAIL      27.00 seconds
TestRunnerSetup               PASS      746.24 seconds
TestRunner_l2cap-tester       PASS      15.07 seconds
TestRunner_iso-tester         PASS      13.16 seconds
TestRunner_bnep-tester        PASS      3.20 seconds
TestRunner_mgmt-tester        PASS      89.06 seconds
TestRunner_rfcomm-tester      PASS      4.51 seconds
TestRunner_sco-tester         PASS      5.66 seconds
TestRunner_ioctl-tester       PASS      4.72 seconds
TestRunner_mesh-tester        PASS      5.57 seconds
TestRunner_smp-tester         PASS      4.37 seconds
TestRunner_userchan-tester    PASS      3.24 seconds
TestRunner_6lowpan-tester     PASS      4.47 seconds
IncrementalBuild              PASS      28.98 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: L2CAP: check security before completing a deferred BR/EDR accept
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#122: 
The child channel is placed on the parent's accept queue at CONN_REQ time and

total: 0 errors, 1 warnings, 0 checks, 36 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.

/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14998992.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: CheckKernelLLVM - FAIL
Desc: Build kernel with LLVM + context analysis
Output:

net/bluetooth/l2cap_sock.c:1277:14: error: acquiring mutex 'sk->chan->conn->lock' that is already held [-Werror,-Wthread-safety-analysis]
 1277 |         have_conn = l2cap_chan_lock_conn(chan);
      |                     ^
net/bluetooth/l2cap_sock.c:1277:14: note: mutex acquired here
net/bluetooth/l2cap_sock.c:1302:5: error: mutex 'sk->chan->conn->lock' is not held on every path through here [-Werror,-Wthread-safety-analysis]
 1302 |                                 l2cap_chan_unlock_conn(chan, have_conn);
      |                                 ^
./include/net/bluetooth/l2cap.h:1025:2: note: expanded from macro 'l2cap_chan_unlock_conn'
 1025 |         ({                                                              \
      |         ^
net/bluetooth/l2cap_sock.c:1277:14: note: mutex acquired here
 1277 |         have_conn = l2cap_chan_lock_conn(chan);
      |                     ^
2 errors generated.
make[4]: *** [scripts/Makefile.build:290: net/bluetooth/l2cap_sock.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [scripts/Makefile.build:572: net/bluetooth] Error 2
make[2]: *** [scripts/Makefile.build:572: net] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/home/runner/work/bluetooth-next/bluetooth-next/src/src/Makefile:2243: .] Error 2
make: *** [Makefile:248: __sub-make] Error 2


https://github.com/bluez/bluetooth-next/pull/1153

---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2026-11-19  1:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 21:33 [PATCH] Bluetooth: L2CAP: check security before completing a deferred BR/EDR accept Mohammed Alquraini
2026-11-18 23:04 ` Luiz Augusto von Dentz
2026-11-19  1:07 ` 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=6afe4bbe.5da39d67.21e96f.ecd1@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mohammed.saad.alquraini@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