RE: [v5] Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery

[bluez.test.bot@gmail.com]

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.15 seconds
VerifyFixes                   PASS      0.43 seconds
VerifySignedoff               PASS      0.09 seconds
GitLint                       PASS      0.27 seconds
SubjectPrefix                 PASS      0.08 seconds
BuildKernel                   PASS      30.64 seconds
CheckAllWarning               PASS      34.89 seconds
CheckSparse                   WARNING   39.31 seconds
BuildKernel32                 PASS      30.78 seconds
CheckKernelLLVM               PASS      31.92 seconds
TestRunnerSetup               PASS      700.26 seconds
TestRunner_l2cap-tester       FAIL      10.54 seconds
TestRunner_iso-tester         PASS      10.50 seconds
TestRunner_bnep-tester        PASS      3.15 seconds
TestRunner_mgmt-tester        PASS      87.46 seconds
TestRunner_rfcomm-tester      PASS      4.50 seconds
TestRunner_sco-tester         PASS      5.57 seconds
TestRunner_ioctl-tester       PASS      4.65 seconds
TestRunner_mesh-tester        PASS      5.52 seconds
TestRunner_smp-tester         PASS      4.35 seconds
TestRunner_userchan-tester    PASS      3.22 seconds
TestRunner_6lowpan-tester     PASS      4.40 seconds
IncrementalBuild              PASS      28.90 seconds

Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==35==ERROR: AddressSanitizer: heap-use-after-free on address 0x7c0351fe33d0 at pc 0x55973e00ee8e bp 0x7ffe21df4d40 sp 0x7ffe21df4d30
READ of size 4 at 0x7c0351fe33d0 thread T0
    #0 0x55973e00ee8d in timeout_callback src/shared/timeout-mainloop.c:33
    #1 0x55973e00fb75 in timeout_callback src/shared/mainloop.c:270
    #2 0x55973e010aa6 in mainloop_run src/shared/mainloop.c:124
    #3 0x55973e0133fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
    #4 0x55973e01864b in tester_run src/shared/tester.c:1223
    #5 0x55973df4217d in main tools/l2cap-tester.c:3918
    #6 0x7fc352f45600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
    #7 0x7fc352f45717 in __libc_start_main_impl ../csu/libc-start.c:360
    #8 0x55973df48c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)

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

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

---
Regards,
Linux Bluetooth