From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, loic.poulain@oss.qualcomm.com
Subject: RE: Support for block device NVMEM providers
Date: Mon, 02 Nov 2026 11:29:35 -0800 (PST) [thread overview]
Message-ID: <6ae8e49f.8f9f3ad8.7b6f1.58ed@mx.google.com> (raw)
In-Reply-To: <20261102-block-as-nvmem-v12-1-f4a2a681087d@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 4186 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/1199253/
---Test result---
Test Summary:
CheckPatch FAIL 6.22 seconds
VerifyFixes PASS 7.99 seconds
VerifySignedoff PASS 1.42 seconds
GitLint PASS 0.62 seconds
SubjectPrefix FAIL 0.31 seconds
BuildKernel PASS 20.57 seconds
CheckAllWarning PASS 24.52 seconds
CheckSparse PASS 25.22 seconds
BuildKernel32 PASS 21.19 seconds
CheckKernelLLVM PASS 20.60 seconds
TestRunnerSetup PASS 472.16 seconds
TestRunner_l2cap-tester FAIL 12.07 seconds
TestRunner_iso-tester PASS 11.27 seconds
TestRunner_bnep-tester PASS 2.80 seconds
TestRunner_mgmt-tester PASS 83.15 seconds
TestRunner_rfcomm-tester PASS 4.02 seconds
TestRunner_sco-tester PASS 5.02 seconds
TestRunner_ioctl-tester PASS 4.19 seconds
TestRunner_mesh-tester PASS 5.04 seconds
TestRunner_smp-tester PASS 3.98 seconds
TestRunner_userchan-tester PASS 2.87 seconds
TestRunner_6lowpan-tester PASS 12.85 seconds
IncrementalBuild PASS 38.56 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v12,2/2] block: implement NVMEM provider
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#266:
new file mode 100644
total: 0 errors, 1 warnings, 194 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/14936682.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: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==38==ERROR: AddressSanitizer: heap-use-after-free on address 0x7c37651e33d0 at pc 0x55ad034d8e8e bp 0x7ffc16b95f60 sp 0x7ffc16b95f50
READ of size 4 at 0x7c37651e33d0 thread T0
#0 0x55ad034d8e8d in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x55ad034d9b75 in timeout_callback src/shared/mainloop.c:270
#2 0x55ad034daaa6 in mainloop_run src/shared/mainloop.c:124
#3 0x55ad034dd3fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x55ad034e264b in tester_run src/shared/tester.c:1223
#5 0x55ad0340c17d in main tools/l2cap-tester.c:3918
#6 0x7ff766178600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7ff766178717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x55ad03412c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)
0x7c37651e33d0 is located 0 bytes inside of 40-byte region [0x7c37651e33d0,0x7c37651e33f8)
freed by thread T0 here:
#0 0x7ff766ab63ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x55ad034d936a in timeout_destroy src/shared/mainloop.c:251
previously allocated by thread T0 here:
#0 0x7ff766ab760f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x55ad034c32d5 in util_malloc src/shared/util.c:46
SUMMARY: AddressSanitizer: heap-use-after-free src/shared/timeout-mainloop.c:33 in timeout_callback
No test result found
https://github.com/bluez/bluetooth-next/pull/1045
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-02 19:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 16:27 [PATCH v12 0/2] Support for block device NVMEM providers Loic Poulain
2026-11-02 16:27 ` [PATCH v12 1/2] block: partitions: of: Attach partition fwnode to the block device Loic Poulain
2026-11-02 19:29 ` bluez.test.bot [this message]
2026-11-06 18:41 ` Ulf Hansson
2026-11-02 16:27 ` [PATCH v12 2/2] block: implement NVMEM provider Loic Poulain
2026-11-03 9:56 ` Christoph Hellwig
2026-11-03 16:27 ` sashiko-bot
-- strict thread matches above, loose matches on Subject: below --
2026-10-15 14:26 [PATCH v11 1/7] dt-bindings: bluetooth: qcom: Add NVMEM BD address cell Loic Poulain
2026-10-15 16:44 ` Support for block device NVMEM providers bluez.test.bot
2026-08-06 14:38 [PATCH v10 01/10] dt-bindings: mmc: Document fixed-layout NVMEM provider support Loic Poulain
2026-08-07 1:23 ` Support for block device NVMEM providers bluez.test.bot
2026-07-30 16:00 [PATCH v9 01/10] dt-bindings: mmc: Document fixed-layout NVMEM provider support Loic Poulain
2026-07-30 17:30 ` Support for block device NVMEM providers bluez.test.bot
2026-07-03 13:45 [PATCH v8 1/9] dt-bindings: mmc: Document fixed-layout NVMEM provider support Loic Poulain
2026-07-03 16:12 ` Support for block device NVMEM providers bluez.test.bot
2026-07-01 16:00 [PATCH v7 1/9] dt-bindings: mmc: Document fixed-layout NVMEM provider support Loic Poulain
2026-07-01 17:01 ` Support for block device NVMEM providers bluez.test.bot
2026-06-29 8:55 [PATCH v6 1/9] block: partitions: of: Skip child nodes without reg property Loic Poulain
2026-06-29 12:30 ` Support for block device NVMEM providers bluez.test.bot
2026-06-12 13:20 [PATCH v5 1/9] block: partitions: of: Skip child nodes without reg property Loic Poulain
2026-06-12 16:24 ` Support for block device NVMEM providers bluez.test.bot
2026-06-09 7:52 [PATCH v4 1/8] dt-bindings: mmc: Document support for nvmem-layout Loic Poulain
2026-06-09 9:31 ` Support for block device NVMEM providers bluez.test.bot
2026-06-08 10:50 [PATCH v3 1/7] dt-bindings: mmc: Document support for nvmem-layout Loic Poulain
2026-06-08 12:12 ` Support for block device NVMEM providers bluez.test.bot
2026-05-07 15:24 [PATCH v2 1/8] dt-bindings: mmc: Document support for nvmem-layout Loic Poulain
2026-05-07 16:19 ` Support for block device NVMEM providers bluez.test.bot
2026-04-28 14:23 [PATCH 1/9] dt-bindings: mmc: Document support for nvmem-layout Loic Poulain
2026-04-28 17:44 ` Support for block device NVMEM providers 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=6ae8e49f.8f9f3ad8.7b6f1.58ed@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.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.