From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, bence.csokas@arm.com
Subject: RE: Add offsetofp() and offsetofendp() for pointer arithmetic
Date: Thu, 05 Nov 2026 15:16:25 -0800 (PST) [thread overview]
Message-ID: <6aed0e49.a1b259eb.344405.2759@mx.google.com> (raw)
In-Reply-To: <20261105-offsetof-v1-1-4153f5c10edc@arm.com>
[-- Attachment #1: Type: text/plain, Size: 4322 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/1203387/
---Test result---
Test Summary:
CheckPatch FAIL 11.80 seconds
VerifyFixes PASS 0.06 seconds
VerifySignedoff PASS 0.07 seconds
GitLint PASS 0.62 seconds
SubjectPrefix FAIL 0.35 seconds
BuildKernel PASS 28.73 seconds
CheckAllWarning PASS 32.78 seconds
CheckSparse PASS 35.19 seconds
BuildKernel32 PASS 28.58 seconds
CheckKernelLLVM PASS 30.98 seconds
TestRunnerSetup PASS 695.81 seconds
TestRunner_l2cap-tester FAIL 10.46 seconds
TestRunner_iso-tester PASS 12.58 seconds
TestRunner_bnep-tester PASS 2.96 seconds
TestRunner_mgmt-tester PASS 87.04 seconds
TestRunner_rfcomm-tester PASS 6.73 seconds
TestRunner_sco-tester PASS 6.73 seconds
TestRunner_ioctl-tester PASS 4.43 seconds
TestRunner_mesh-tester PASS 5.55 seconds
TestRunner_smp-tester PASS 9.02 seconds
TestRunner_userchan-tester PASS 9.13 seconds
TestRunner_6lowpan-tester PASS 5.75 seconds
IncrementalBuild PASS 29.94 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[3/3] treewide: Use offsetofp()
WARNING: line length of 107 exceeds 100 columns
#483: FILE: drivers/gpu/drm/drm_edid.c:3254:
+ BUILD_BUG_ON(offsetofp(descriptor, data.other_data.data.range.formula.gtf2.hfreq_start_khz) != 12);
total: 0 errors, 1 warnings, 539 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/14954507.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
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==36==ERROR: AddressSanitizer: heap-use-after-free on address 0x7c28be8e33d0 at pc 0x5648ef767eee bp 0x7ffcda785f60 sp 0x7ffcda785f50
READ of size 4 at 0x7c28be8e33d0 thread T0
#0 0x5648ef767eed in timeout_callback src/shared/timeout-mainloop.c:33
#1 0x5648ef768ed5 in timeout_callback src/shared/mainloop.c:271
#2 0x5648ef76a006 in mainloop_run src/shared/mainloop.c:125
#3 0x5648ef76c96a in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#4 0x5648ef771c4b in tester_run src/shared/tester.c:1297
#5 0x5648ef69b1dd in main tools/l2cap-tester.c:3918
#6 0x7fe8bf7e6600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
#7 0x7fe8bf7e6717 in __libc_start_main_impl ../csu/libc-start.c:360
#8 0x5648ef6a1ce4 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16dce4) (BuildId: 0d2067a7ef8fe61fcf622598953c7d0f996221a0)
0x7c28be8e33d0 is located 0 bytes inside of 40-byte region [0x7c28be8e33d0,0x7c28be8e33f8)
freed by thread T0 here:
#0 0x7fe8c01243ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x5648ef7683ca in timeout_destroy src/shared/mainloop.c:252
previously allocated by thread T0 here:
#0 0x7fe8c012560f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
#1 0x5648ef752335 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/1072
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-05 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 17:16 [PATCH 0/3] Add offsetofp() and offsetofendp() for pointer arithmetic Bence Csokas
2026-11-05 17:16 ` [PATCH 1/3] stddef: " Bence Csokas
2026-11-05 23:16 ` bluez.test.bot [this message]
2026-11-05 17:16 ` [PATCH 2/3] treewide: Use offsetofendp() Bence Csokas
2026-11-05 17:16 ` [PATCH 3/3] treewide: Use offsetofp() Bence Csokas
2026-11-06 8:04 ` [PATCH 0/3] Add offsetofp() and offsetofendp() for pointer arithmetic Christoph Hellwig
2026-11-06 8:29 ` Bence Csókás
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=6aed0e49.a1b259eb.344405.2759@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=bence.csokas@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox