From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, v4bel@theori.io
Subject: RE: [v2] Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg
Date: Sat, 09 Dec 2023 03:30:34 -0800 (PST) [thread overview]
Message-ID: <65744fda.050a0220.55a3e.6adf@mx.google.com> (raw)
In-Reply-To: <20231209105518.GA408904@v4bel-B760M-AORUS-ELITE-AX>
[-- Attachment #1: Type: text/plain, Size: 1666 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=808455
---Test result---
Test Summary:
CheckPatch PASS 0.65 seconds
GitLint PASS 1.39 seconds
SubjectPrefix PASS 0.63 seconds
BuildKernel PASS 26.92 seconds
CheckAllWarning PASS 30.69 seconds
CheckSparse WARNING 35.03 seconds
CheckSmatch PASS 98.43 seconds
BuildKernel32 PASS 26.94 seconds
TestRunnerSetup PASS 429.62 seconds
TestRunner_l2cap-tester PASS 23.37 seconds
TestRunner_iso-tester PASS 45.83 seconds
TestRunner_bnep-tester PASS 6.95 seconds
TestRunner_mgmt-tester PASS 162.57 seconds
TestRunner_rfcomm-tester PASS 10.76 seconds
TestRunner_sco-tester PASS 14.44 seconds
TestRunner_ioctl-tester PASS 11.75 seconds
TestRunner_mesh-tester PASS 8.64 seconds
TestRunner_smp-tester PASS 9.63 seconds
TestRunner_userchan-tester PASS 7.28 seconds
IncrementalBuild PASS 25.21 seconds
Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/af_bluetooth.c:223:25: warning: context imbalance in 'bt_accept_enqueue' - different lock contexts for basic block
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-12-09 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 10:55 [PATCH v2] Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg Hyunwoo Kim
2023-12-09 11:30 ` bluez.test.bot [this message]
2023-12-15 16:00 ` patchwork-bot+bluetooth
2024-02-22 11:23 ` Martyn Welch
2024-04-22 23:49 ` Hyunwoo Kim
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=65744fda.050a0220.55a3e.6adf@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=v4bel@theori.io \
/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;
as well as URLs for NNTP newsgroup(s).