All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, radek@podgorny.cz
Subject: RE: Bluetooth: find an RPA peer's connection parameters by its identity
Date: Sun, 01 Nov 2026 11:57:36 -0800 (PST)	[thread overview]
Message-ID: <6ae799b0.184146ba.4160.b8f1@mx.google.com> (raw)
In-Reply-To: <20261101-for-upstream-le-conn-params-rpa-v1-1-988629a09bc9@podgorny.cz>

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

---Test result---

Test Summary:
CheckPatch                    PASS      3.92 seconds
VerifyFixes                   PASS      1.28 seconds
VerifySignedoff               PASS      0.11 seconds
GitLint                       PASS      0.31 seconds
SubjectPrefix                 PASS      0.11 seconds
BuildKernel                   PASS      28.99 seconds
CheckAllWarning               PASS      33.23 seconds
CheckSparse                   PASS      35.53 seconds
BuildKernel32                 PASS      29.33 seconds
CheckKernelLLVM               PASS      31.75 seconds
TestRunnerSetup               PASS      678.99 seconds
TestRunner_l2cap-tester       FAIL      12.14 seconds
TestRunner_iso-tester         PASS      10.45 seconds
TestRunner_bnep-tester        PASS      2.99 seconds
TestRunner_mgmt-tester        PASS      86.50 seconds
TestRunner_rfcomm-tester      PASS      4.29 seconds
TestRunner_sco-tester         PASS      5.38 seconds
TestRunner_ioctl-tester       PASS      4.50 seconds
TestRunner_mesh-tester        PASS      5.32 seconds
TestRunner_smp-tester         PASS      4.17 seconds
TestRunner_userchan-tester    PASS      3.06 seconds
TestRunner_6lowpan-tester     PASS      4.24 seconds
IncrementalBuild              PASS      27.60 seconds

Details
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==36==ERROR: AddressSanitizer: heap-use-after-free on address 0x7b926a3e33d0 at pc 0x556ffff58e8e bp 0x7ffc6f1889b0 sp 0x7ffc6f1889a0
READ of size 4 at 0x7b926a3e33d0 thread T0
    #0 0x556ffff58e8d in timeout_callback src/shared/timeout-mainloop.c:33
    #1 0x556ffff59b75 in timeout_callback src/shared/mainloop.c:270
    #2 0x556ffff5aaa6 in mainloop_run src/shared/mainloop.c:124
    #3 0x556ffff5d3fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
    #4 0x556ffff6264b in tester_run src/shared/tester.c:1223
    #5 0x556fffe8c17d in main tools/l2cap-tester.c:3918
    #6 0x7f526b350600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
    #7 0x7f526b350717 in __libc_start_main_impl ../csu/libc-start.c:360
    #8 0x556fffe92c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)

0x7b926a3e33d0 is located 0 bytes inside of 40-byte region [0x7b926a3e33d0,0x7b926a3e33f8)
freed by thread T0 here:
    #0 0x7f526bc8e3ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
    #1 0x556ffff5936a in timeout_destroy src/shared/mainloop.c:251

previously allocated by thread T0 here:
    #0 0x7f526bc8f60f in malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:67
    #1 0x556ffff432d5 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/1037

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-11-01 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-01 17:20 [PATCH] Bluetooth: find an RPA peer's connection parameters by its identity Radek Podgorny
2026-11-01 19:57 ` 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=6ae799b0.184146ba.4160.b8f1@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=radek@podgorny.cz \
    /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.