All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: MGMT: Serialize power-on with power-off completion
Date: Tue, 13 Oct 2026 13:19:27 -0700 (PDT)	[thread overview]
Message-ID: <6ace924f.14693a91.2cb03e.a9bb@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0063-v7-35a6680c94a332fea155@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.60 seconds
VerifyFixes                   PASS      0.06 seconds
VerifySignedoff               PASS      0.06 seconds
GitLint                       PASS      11.67 seconds
SubjectPrefix                 PASS      1.12 seconds
BuildKernel                   PASS      30.33 seconds
CheckAllWarning               PASS      35.37 seconds
CheckSparse                   PASS      37.26 seconds
BuildKernel32                 PASS      29.76 seconds
CheckKernelLLVM               FAIL      23.97 seconds
TestRunnerSetup               PASS      729.63 seconds
TestRunner_mgmt-tester        PASS      87.68 seconds
TestRunner_mesh-tester        PASS      5.48 seconds
IncrementalBuild              PASS      27.87 seconds

Details
##############################
Test: CheckKernelLLVM - FAIL
Desc: Build kernel with LLVM + context analysis
Output:

net/bluetooth/mgmt.c:1418:2: error: mutex 'hdev->req_lock' is not held on every path through here [-Werror,-Wthread-safety-analysis]
 1418 |         hci_dev_lock(hdev);
      |         ^
./include/net/bluetooth/hci_core.h:1799:26: note: expanded from macro 'hci_dev_lock'
 1799 | #define hci_dev_lock(d)         mutex_lock(&d->lock)
      |                                 ^
net/bluetooth/mgmt.c:1416:3: note: mutex acquired here
 1416 |                 hci_req_sync_lock(hdev);
      |                 ^
./include/net/bluetooth/hci_sync.h:15:35: note: expanded from macro 'hci_req_sync_lock'
   15 | #define hci_req_sync_lock(hdev)   mutex_lock(&hdev->req_lock)
      |                                   ^
net/bluetooth/mgmt.c:1462:3: error: releasing mutex 'hdev->req_lock' that was not held [-Werror,-Wthread-safety-analysis]
 1462 |                 hci_req_sync_unlock(hdev);
      |                 ^
./include/net/bluetooth/hci_sync.h:16:35: note: expanded from macro 'hci_req_sync_unlock'
   16 | #define hci_req_sync_unlock(hdev) mutex_unlock(&hdev->req_lock)
      |                                   ^
2 errors generated.
make[4]: *** [scripts/Makefile.build:290: net/bluetooth/mgmt.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [scripts/Makefile.build:551: net/bluetooth] Error 2
make[2]: *** [scripts/Makefile.build:551: net] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/home/runner/work/bluetooth-next/bluetooth-next/src/src/Makefile:2229: .] Error 2
make: *** [Makefile:248: __sub-make] Error 2


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

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-10-13 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 16:28 [PATCH] Bluetooth: MGMT: Serialize power-on with power-off completion Cen Zhang
2026-10-13 20:19 ` 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=6ace924f.14693a91.2cb03e.a9bb@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zzzccc427@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.