All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, bsdhenrymartin@gmail.com
Subject: RE: Bluetooth: RFCOMM: fix race on dlc->session in RFCOMM_CONNINFO getsockopt
Date: Fri, 20 Nov 2026 05:37:03 -0800 (PST)	[thread overview]
Message-ID: <6b004cff.a5690e37.19a5c8.ae7a@mx.google.com> (raw)
In-Reply-To: <20261120063343.3875317-1-bsdhenrymartin@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4094 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/1216976/

---Test result---

Test Summary:
CheckPatch                    FAIL      1.12 seconds
VerifyFixes                   PASS      0.07 seconds
VerifySignedoff               PASS      0.08 seconds
GitLint                       FAIL      0.24 seconds
SubjectPrefix                 PASS      0.07 seconds
BuildKernel                   PASS      32.33 seconds
CheckAllWarning               PASS      37.18 seconds
CheckSparse                   PASS      39.30 seconds
BuildKernel32                 PASS      32.79 seconds
CheckKernelLLVM               FAIL      34.47 seconds
TestRunnerSetup               PASS      763.09 seconds
TestRunner_l2cap-tester       PASS      14.77 seconds
TestRunner_iso-tester         PASS      13.11 seconds
TestRunner_bnep-tester        PASS      3.15 seconds
TestRunner_mgmt-tester        PASS      89.65 seconds
TestRunner_rfcomm-tester      PASS      4.52 seconds
TestRunner_sco-tester         PASS      5.69 seconds
TestRunner_ioctl-tester       PASS      4.68 seconds
TestRunner_mesh-tester        PASS      4.53 seconds
TestRunner_smp-tester         PASS      4.41 seconds
TestRunner_userchan-tester    PASS      3.23 seconds
TestRunner_6lowpan-tester     PASS      4.47 seconds
IncrementalBuild              PASS      30.03 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: RFCOMM: fix race on dlc->session in RFCOMM_CONNINFO getsockopt
WARNING: The commit message has 'stable@', perhaps it also needs a 'Fixes:' tag?

total: 0 errors, 1 warnings, 0 checks, 67 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/15004442.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: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: RFCOMM: fix race on dlc->session in RFCOMM_CONNINFO getsockopt

6: B3 Line contains hard tab characters (\t): "	l2cap_sk = rfcomm_pi(sk)->dlc->session->sock->sk;"
##############################
Test: CheckKernelLLVM - FAIL
Desc: Build kernel with LLVM + context analysis
Output:

net/bluetooth/rfcomm/sock.c:771:2: error: mutex 'rfcomm_mutex' is not held on every path through here [-Werror,-Wthread-safety-analysis]
  771 |         lock_sock(sk);
      |         ^
net/bluetooth/rfcomm/sock.c:769:3: note: mutex acquired here
  769 |                 rfcomm_lock();
      |                 ^
./include/net/bluetooth/rfcomm.h:152:23: note: expanded from macro 'rfcomm_lock'
  152 | #define rfcomm_lock()   mutex_lock(&rfcomm_mutex)
      |                         ^
net/bluetooth/rfcomm/sock.c:833:3: error: releasing mutex 'rfcomm_mutex' that was not held [-Werror,-Wthread-safety-analysis]
  833 |                 rfcomm_unlock();
      |                 ^
./include/net/bluetooth/rfcomm.h:153:25: note: expanded from macro 'rfcomm_unlock'
  153 | #define rfcomm_unlock() mutex_unlock(&rfcomm_mutex)
      |                         ^
2 errors generated.
make[5]: *** [scripts/Makefile.build:290: net/bluetooth/rfcomm/sock.o] Error 1
make[4]: *** [scripts/Makefile.build:572: net/bluetooth/rfcomm] Error 2
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/1165

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-11-20 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20  6:33 [PATCH] Bluetooth: RFCOMM: fix race on dlc->session in RFCOMM_CONNINFO getsockopt Henry Martin
2026-11-20 13:37 ` 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=6b004cff.a5690e37.19a5c8.ae7a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=bsdhenrymartin@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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 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.