All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, benquike@gmail.com
Subject: RE: Bluetooth: RFCOMM: fix NULL dereference of dlc->session in RFCOMM_CONNINFO
Date: Sat, 19 Sep 2026 05:20:25 -0700 (PDT)	[thread overview]
Message-ID: <6aae7e09.90f82e37.2dfa5f.274e@mx.google.com> (raw)
In-Reply-To: <20260919091120.3273038-1-benquike@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.76 seconds
VerifyFixes                   PASS      0.13 seconds
VerifySignedoff               PASS      0.13 seconds
GitLint                       FAIL      0.33 seconds
SubjectPrefix                 PASS      0.12 seconds
BuildKernel                   PASS      28.91 seconds
CheckAllWarning               PASS      33.09 seconds
CheckSparse                   PASS      35.63 seconds
BuildKernel32                 PASS      28.67 seconds
CheckKernelLLVM               PASS      34.55 seconds
TestRunnerSetup               PASS      773.03 seconds
TestRunner_rfcomm-tester      PASS      5.65 seconds
IncrementalBuild              PASS      26.72 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: RFCOMM: fix NULL dereference of dlc->session in RFCOMM_CONNINFO
WARNING: The commit message has 'Call Trace:', perhaps it also needs a 'Fixes:' tag?

total: 0 errors, 1 warnings, 0 checks, 12 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14831156.patch has style problems, please review.

NOTE: Ignored message types: UNKNOWN_COMMIT_ID

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.


##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: RFCOMM: fix NULL dereference of dlc->session in RFCOMM_CONNINFO

6: B3 Line contains hard tab characters (\t): "	if (sk->sk_state != BT_CONNECTED &&"
7: B3 Line contains hard tab characters (\t): "				!rfcomm_pi(sk)->dlc->defer_setup) {"
8: B3 Line contains hard tab characters (\t): "		err = -ENOTCONN;"
9: B3 Line contains hard tab characters (\t): "		break;"
10: B3 Line contains hard tab characters (\t): "	}"
11: B3 Line contains hard tab characters (\t): "	l2cap_sk = rfcomm_pi(sk)->dlc->session->sock->sk;"


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

---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2026-09-19 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19  9:11 [PATCH] Bluetooth: RFCOMM: fix NULL dereference of dlc->session in RFCOMM_CONNINFO Hui Peng
2026-09-19 11:25 ` [PATCH v2] " Hui Peng
2026-09-19 12:14   ` [v2] " bluez.test.bot
2026-09-21 14:10   ` [PATCH v2] " patchwork-bot+bluetooth
2026-09-19 12:20 ` 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=6aae7e09.90f82e37.2dfa5f.274e@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=benquike@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.