RE: Bluetooth: L2CAP: Match LE responses to outstanding requests

[bluez.test.bot@gmail.com]

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.44 seconds
VerifyFixes                   PASS      0.06 seconds
VerifySignedoff               PASS      0.69 seconds
GitLint                       FAIL      0.42 seconds
SubjectPrefix                 PASS      0.26 seconds
BuildKernel                   PASS      31.81 seconds
CheckAllWarning               PASS      35.83 seconds
CheckSparse                   PASS      38.75 seconds
BuildKernel32                 PASS      31.71 seconds
CheckKernelLLVM               PASS      35.49 seconds
TestRunnerSetup               PASS      754.40 seconds
TestRunner_l2cap-tester       FAIL      10.77 seconds
IncrementalBuild              PASS      33.12 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[1/2] Bluetooth: L2CAP: Only accept LE responses to outstanding requests

24: B1 Line exceeds max length (126>80): "Cc: <stable@vger.kernel.org> # 5.7.x: a518b9a9ef6e: Bluetooth: L2CAP: Only accept connection responses to outstanding requests"
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Sanitizer errors:
==37==ERROR: AddressSanitizer: heap-use-after-free on address 0x7b79aa5e33d0 at pc 0x55a2e85dce8e bp 0x7fff8162f020 sp 0x7fff8162f010
READ of size 4 at 0x7b79aa5e33d0 thread T0
    #0 0x55a2e85dce8d in timeout_callback src/shared/timeout-mainloop.c:33
    #1 0x55a2e85ddb75 in timeout_callback src/shared/mainloop.c:270
    #2 0x55a2e85deaa6 in mainloop_run src/shared/mainloop.c:124
    #3 0x55a2e85e13fa in mainloop_run_with_signal src/shared/mainloop-notify.c:196
    #4 0x55a2e85e664b in tester_run src/shared/tester.c:1223
    #5 0x55a2e851017d in main tools/l2cap-tester.c:3918
    #6 0x7f39ab51c600 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:59
    #7 0x7f39ab51c717 in __libc_start_main_impl ../csu/libc-start.c:360
    #8 0x55a2e8516c84 in _start (/home/runner/work/bluetooth-next/bluetooth-next/src/bluez/tools/l2cap-tester+0x16cc84) (BuildId: 91c9d49e9766c394468e27ffa29b05e7d348169f)

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

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

---
Regards,
Linux Bluetooth