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/project/bluetooth/list/?series=1090104 ---Test result--- Test Summary: CheckPatch PASS 2.70 seconds GitLint FAIL 0.56 seconds SubjectPrefix PASS 0.20 seconds BuildKernel PASS 26.91 seconds CheckAllWarning PASS 29.32 seconds CheckSparse PASS 28.03 seconds BuildKernel32 PASS 25.85 seconds TestRunnerSetup PASS 563.34 seconds TestRunner_l2cap-tester FAIL 18.59 seconds TestRunner_iso-tester PASS 309.82 seconds TestRunner_bnep-tester FAIL 18.21 seconds TestRunner_mgmt-tester FAIL 22.89 seconds TestRunner_rfcomm-tester PASS 40.92 seconds TestRunner_sco-tester PASS 80.08 seconds TestRunner_ioctl-tester FAIL 49.57 seconds TestRunner_mesh-tester PASS 39.00 seconds TestRunner_smp-tester PASS 17.90 seconds TestRunner_userchan-tester PASS 19.79 seconds TestRunner_6lowpan-tester PASS 34.53 seconds IncrementalBuild PASS 42.47 seconds Details ############################## Test: GitLint - FAIL Desc: Run gitlint Output: [v1,1/2] Bluetooth: HCI: Add initial support for Short Connection Interval feature WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search 1: T1 Title exceeds max length (82>80): "[v1,1/2] Bluetooth: HCI: Add initial support for Short Connection Interval feature" ############################## Test: TestRunner_l2cap-tester - FAIL Desc: Run l2cap-tester with test-runner Output: Crash detected: ==34== by 0x13325F: tester_run (tester.c:1085) ==34== by 0x1142AD: main (l2cap-tester.c:3295) ==34== Address 0x50 is not stack'd, malloc'd or (recently) free'd ==34== ==34== ==34== Process terminating with default action of signal 11 (SIGSEGV) ==34== Access not within mapped region at address 0x50 ==34== at 0x12BE24: bthost_set_cmd_complete_cb (bthost.c:3487) ==34== by 0x11596D: setup_powered_client_callback (l2cap-tester.c:1317) ==34== by 0x12E5B0: request_complete (mgmt.c:320) ==34== by 0x12F045: can_read_data (mgmt.c:408) ==34== by 0x131AB8: watch_callback (io-glib.c:173) ==34== by 0x48A304D: g_main_context_dispatch (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A33FF: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A36F2: g_main_loop_run (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x133868: mainloop_run (mainloop-glib.c:65) ==34== by 0x133C9F: mainloop_run_with_signal (mainloop-notify.c:196) ==34== by 0x13325F: tester_run (tester.c:1085) ==34== by 0x1142AD: main (l2cap-tester.c:3295) ==34== If you believe this happened as a result of a stack ==34== overflow in your program's main thread (unlikely but ==34== possible), you can try to increase the size of the ==34== main thread stack using the --main-stacksize= flag. ==34== The main thread stack size used in this run was 8388608. ==34== Valgrind errors: ==34== by 0x11596D: setup_powered_client_callback (l2cap-tester.c:1317) ==34== by 0x12E5B0: request_complete (mgmt.c:320) ==34== by 0x12F045: can_read_data (mgmt.c:408) ==34== by 0x131AB8: watch_callback (io-glib.c:173) ==34== by 0x48A304D: g_main_context_dispatch (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A33FF: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A36F2: g_main_loop_run (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x133868: mainloop_run (mainloop-glib.c:65) ==34== by 0x133C9F: mainloop_run_with_signal (mainloop-notify.c:196) ==34== by 0x13325F: tester_run (tester.c:1085) ==34== by 0x1142AD: main (l2cap-tester.c:3295) ==34== If you believe this happened as a result of a stack ==34== overflow in your program's main thread (unlikely but ==34== possible), you can try to increase the size of the ==34== main thread stack using the --main-stacksize= flag. ==34== The main thread stack size used in this run was 8388608. ==34== ==34== HEAP SUMMARY: ==34== in use at exit: 66,134 bytes in 464 blocks ==34== total heap usage: 632 allocs, 168 frees, 80,436 bytes allocated ==34== ==34== LEAK SUMMARY: ==34== definitely lost: 0 bytes in 0 blocks ==34== indirectly lost: 0 bytes in 0 blocks ==34== possibly lost: 0 bytes in 0 blocks ==34== still reachable: 66,134 bytes in 464 blocks ==34== suppressed: 0 bytes in 0 blocks ==34== Rerun with --leak-check=full to see details of leaked memory ==34== ==34== For lists of detected and suppressed errors, rerun with: -s ==34== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0) Crash detected: ==34== suppressed: 0 bytes in 0 blocks ==34== Rerun with --leak-check=full to see details of leaked memory ==34== ==34== For lists of detected and suppressed errors, rerun with: -s ==34== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0) Segmentation fault Process 33 exited with status 139 reboot: Restarting system reboot: machine restart No test result found ############################## Test: TestRunner_bnep-tester - FAIL Desc: Run bnep-tester with test-runner Output: Crash detected: ==34== by 0x12C99F: tester_run (tester.c:1085) ==34== by 0x111CB3: main (bnep-tester.c:298) ==34== Address 0x50 is not stack'd, malloc'd or (recently) free'd ==34== ==34== ==34== Process terminating with default action of signal 11 (SIGSEGV) ==34== Access not within mapped region at address 0x50 ==34== at 0x125C44: bthost_set_cmd_complete_cb (bthost.c:3487) ==34== by 0x111F42: setup_powered_client_callback (bnep-tester.c:244) ==34== by 0x127F00: request_complete (mgmt.c:320) ==34== by 0x1288B5: can_read_data (mgmt.c:408) ==34== by 0x12B328: watch_callback (io-glib.c:173) ==34== by 0x48A304D: g_main_context_dispatch (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A33FF: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A36F2: g_main_loop_run (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x12CFA8: mainloop_run (mainloop-glib.c:65) ==34== by 0x12D3DF: mainloop_run_with_signal (mainloop-notify.c:196) ==34== by 0x12C99F: tester_run (tester.c:1085) ==34== by 0x111CB3: main (bnep-tester.c:298) ==34== If you believe this happened as a result of a stack ==34== overflow in your program's main thread (unlikely but ==34== possible), you can try to increase the size of the ==34== main thread stack using the --main-stacksize= flag. ==34== The main thread stack size used in this run was 8388608. ==34== Valgrind errors: ==34== by 0x111F42: setup_powered_client_callback (bnep-tester.c:244) ==34== by 0x127F00: request_complete (mgmt.c:320) ==34== by 0x1288B5: can_read_data (mgmt.c:408) ==34== by 0x12B328: watch_callback (io-glib.c:173) ==34== by 0x48A304D: g_main_context_dispatch (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A33FF: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A36F2: g_main_loop_run (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x12CFA8: mainloop_run (mainloop-glib.c:65) ==34== by 0x12D3DF: mainloop_run_with_signal (mainloop-notify.c:196) ==34== by 0x12C99F: tester_run (tester.c:1085) ==34== by 0x111CB3: main (bnep-tester.c:298) ==34== If you believe this happened as a result of a stack ==34== overflow in your program's main thread (unlikely but ==34== possible), you can try to increase the size of the ==34== main thread stack using the --main-stacksize= flag. ==34== The main thread stack size used in this run was 8388608. ==34== ==34== HEAP SUMMARY: ==34== in use at exit: 25,333 bytes in 82 blocks ==34== total heap usage: 237 allocs, 155 frees, 39,167 bytes allocated ==34== ==34== LEAK SUMMARY: ==34== definitely lost: 0 bytes in 0 blocks ==34== indirectly lost: 0 bytes in 0 blocks ==34== possibly lost: 0 bytes in 0 blocks ==34== still reachable: 25,333 bytes in 82 blocks ==34== suppressed: 0 bytes in 0 blocks ==34== Rerun with --leak-check=full to see details of leaked memory ==34== ==34== For lists of detected and suppressed errors, rerun with: -s ==34== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) Crash detected: ==34== suppressed: 0 bytes in 0 blocks ==34== Rerun with --leak-check=full to see details of leaked memory ==34== ==34== For lists of detected and suppressed errors, rerun with: -s ==34== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) Segmentation fault Process 33 exited with status 139 reboot: Restarting system reboot: machine restart No test result found ############################## Test: TestRunner_mgmt-tester - FAIL Desc: Run mgmt-tester with test-runner Output: Crash detected: ==34== by 0x14F1DF: tester_run (tester.c:1085) ==34== by 0x12B999: main (mgmt-tester.c:15134) ==34== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==34== ==34== ==34== Process terminating with default action of signal 11 (SIGSEGV) ==34== Access not within mapped region at address 0x0 ==34== at 0x145134: bthost_notify_ready (bthost.c:1190) ==34== by 0x12FA10: read_info_callback (mgmt-tester.c:223) ==34== by 0x14A420: request_complete (mgmt.c:320) ==34== by 0x14AFD5: can_read_data (mgmt.c:408) ==34== by 0x14DA48: watch_callback (io-glib.c:173) ==34== by 0x48A304D: g_main_context_dispatch (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A33FF: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A36F2: g_main_loop_run (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x14F7E8: mainloop_run (mainloop-glib.c:65) ==34== by 0x14FC1F: mainloop_run_with_signal (mainloop-notify.c:196) ==34== by 0x14F1DF: tester_run (tester.c:1085) ==34== by 0x12B999: main (mgmt-tester.c:15134) ==34== If you believe this happened as a result of a stack ==34== overflow in your program's main thread (unlikely but ==34== possible), you can try to increase the size of the ==34== main thread stack using the --main-stacksize= flag. ==34== The main thread stack size used in this run was 8388608. ==34== Valgrind errors: ==34== by 0x12FA10: read_info_callback (mgmt-tester.c:223) ==34== by 0x14A420: request_complete (mgmt.c:320) ==34== by 0x14AFD5: can_read_data (mgmt.c:408) ==34== by 0x14DA48: watch_callback (io-glib.c:173) ==34== by 0x48A304D: g_main_context_dispatch (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A33FF: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x48A36F2: g_main_loop_run (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6) ==34== by 0x14F7E8: mainloop_run (mainloop-glib.c:65) ==34== by 0x14FC1F: mainloop_run_with_signal (mainloop-notify.c:196) ==34== by 0x14F1DF: tester_run (tester.c:1085) ==34== by 0x12B999: main (mgmt-tester.c:15134) ==34== If you believe this happened as a result of a stack ==34== overflow in your program's main thread (unlikely but ==34== possible), you can try to increase the size of the ==34== main thread stack using the --main-stacksize= flag. ==34== The main thread stack size used in this run was 8388608. ==34== ==34== HEAP SUMMARY: ==34== in use at exit: 182,331 bytes in 2,112 blocks ==34== total heap usage: 2,379 allocs, 267 frees, 204,063 bytes allocated ==34== ==34== LEAK SUMMARY: ==34== definitely lost: 0 bytes in 0 blocks ==34== indirectly lost: 0 bytes in 0 blocks ==34== possibly lost: 0 bytes in 0 blocks ==34== still reachable: 182,331 bytes in 2,112 blocks ==34== suppressed: 0 bytes in 0 blocks ==34== Rerun with --leak-check=full to see details of leaked memory ==34== ==34== For lists of detected and suppressed errors, rerun with: -s ==34== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) Crash detected: ==34== suppressed: 0 bytes in 0 blocks ==34== Rerun with --leak-check=full to see details of leaked memory ==34== ==34== For lists of detected and suppressed errors, rerun with: -s ==34== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) Segmentation fault Process 33 exited with status 139 reboot: Restarting system reboot: machine restart No test result found ############################## Test: TestRunner_ioctl-tester - FAIL Desc: Run ioctl-tester with test-runner Output: Total: 28, Passed: 0 (0.0%), Failed: 11, Not Run: 17 Failed Test Cases Device List Timed out -31.727 seconds Device Info Timed out -6.903 seconds Reset Stat Timed out -6.909 seconds Set Link Mode - ACCEPT Timed out -6.915 seconds Set Pkt Type - DM Timed out -15.155 seconds Set Pkt Type - DH Timed out -15.162 seconds Set Pkt Type - HV Timed out -15.167 seconds Set Pkt Type - 2-DH Timed out -15.174 seconds Set Pkt Type - 2-DH Timed out -15.181 seconds Set Pkt Type - ALL Timed out -15.187 seconds Set ACL MTU - 1 Timed out -15.192 seconds https://github.com/bluez/bluetooth-next/pull/147 --- Regards, Linux Bluetooth