Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, oss@fourdim.xyz
Subject: RE: Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb()
Date: Fri, 12 Jun 2026 09:17:38 -0700 (PDT)	[thread overview]
Message-ID: <6a2c3122.a342f677.387e91.4350@mx.google.com> (raw)
In-Reply-To: <20260612143449.3045055-2-oss@fourdim.xyz>

[-- Attachment #1: Type: text/plain, Size: 1748 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/project/bluetooth/list/?series=1110715

---Test result---

Test Summary:
CheckPatch                    PASS      1.69 seconds
VerifyFixes                   PASS      0.13 seconds
VerifySignedoff               PASS      0.13 seconds
GitLint                       PASS      0.32 seconds
SubjectPrefix                 PASS      0.12 seconds
BuildKernel                   PASS      27.75 seconds
CheckAllWarning               PASS      30.27 seconds
CheckSparse                   PASS      28.78 seconds
BuildKernel32                 PASS      26.04 seconds
TestRunnerSetup               PASS      593.41 seconds
TestRunner_l2cap-tester       PASS      59.89 seconds
TestRunner_smp-tester         PASS      23.36 seconds
TestRunner_6lowpan-tester     FAIL      45.88 seconds
IncrementalBuild              PASS      25.58 seconds

Details
##############################
Test: TestRunner_6lowpan-tester - FAIL
Desc: Run 6lowpan-tester with test-runner
Output:
Total: 8, Passed: 3 (37.5%), Failed: 5, Not Run: 0

Failed Test Cases
Client Connect - Disconnect                          Timed out    4.974 seconds
Client Recv Dgram - Success                          Timed out    4.990 seconds
Client Recv Raw - Success                            Timed out    5.000 seconds
Client Recv IPHC Dgram - Success                     Timed out    4.991 seconds
Client Recv IPHC Raw - Success                       Timed out    4.997 seconds


https://github.com/bluez/bluetooth-next/pull/309

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-06-12 16:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 14:34 [PATCH v11 0/1] Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb() Siwei Zhang
2026-06-12 14:34 ` [PATCH v11 1/1] " Siwei Zhang
2026-06-12 16:17   ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-11 15:08 [PATCH v10 " Siwei Zhang
2026-06-11 19:09 ` bluez.test.bot
2026-06-03 15:06 [PATCH v9 1/1] " Siwei Zhang
2026-06-03 17:40 ` bluez.test.bot
2026-06-02 12:55 [PATCH v8 1/1] " Siwei Zhang
2026-06-02 15:27 ` bluez.test.bot
2026-06-01 14:03 [PATCH v7 1/1] " Siwei Zhang
2026-06-01 18:50 ` bluez.test.bot
2026-05-29 16:54 [PATCH v6 1/1] " Siwei Zhang
2026-05-29 18:21 ` bluez.test.bot
2026-05-20 16:20 [PATCH v5 1/1] " Siwei Zhang
2026-05-20 18:07 ` bluez.test.bot
2026-05-11 17:09 [PATCH RESEND v4 1/1] " Siwei Zhang
2026-05-11 18:49 ` bluez.test.bot
2026-05-11  4:51 [PATCH 1/1] " Siwei Zhang
2026-05-11  8:32 ` bluez.test.bot
2026-05-11  3:18 [PATCH 1/1] " Siwei Zhang
2026-05-11  4:21 ` bluez.test.bot

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=6a2c3122.a342f677.387e91.4350@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=oss@fourdim.xyz \
    /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