From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, lrh2000@pku.edu.cn
Subject: RE: [v4,1/4] Bluetooth: Fix potential double free caused by hci_conn_unlink
Date: Wed, 03 May 2023 07:38:33 -0700 (PDT) [thread overview]
Message-ID: <645271e9.050a0220.cc54e.ebee@mx.google.com> (raw)
In-Reply-To: <20230503133937.169647-1-lrh2000@pku.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 6704 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=744697
---Test result---
Test Summary:
CheckPatch FAIL 3.22 seconds
GitLint FAIL 1.40 seconds
SubjectPrefix PASS 0.28 seconds
BuildKernel PASS 43.05 seconds
CheckAllWarning PASS 46.73 seconds
CheckSparse PASS 54.02 seconds
CheckSmatch PASS 143.56 seconds
BuildKernel32 PASS 42.36 seconds
TestRunnerSetup PASS 597.83 seconds
TestRunner_l2cap-tester PASS 21.30 seconds
TestRunner_iso-tester PASS 28.00 seconds
TestRunner_bnep-tester PASS 7.24 seconds
TestRunner_mgmt-tester PASS 146.36 seconds
TestRunner_rfcomm-tester PASS 11.56 seconds
TestRunner_sco-tester PASS 10.86 seconds
TestRunner_ioctl-tester PASS 13.13 seconds
TestRunner_mesh-tester PASS 9.28 seconds
TestRunner_smp-tester PASS 10.50 seconds
TestRunner_userchan-tester PASS 7.56 seconds
IncrementalBuild PASS 88.80 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v4,1/4] Bluetooth: Fix potential double free caused by hci_conn_unlink
WARNING: Reported-by: should be immediately followed by Link: with a URL to the report
#82:
Reported-by: syzbot+690b90b14f14f43f4688@syzkaller.appspotmail.com
Closes: https://lore.kernel.org/linux-bluetooth/000000000000484a8205faafe216@google.com/
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#83:
Closes: https://lore.kernel.org/linux-bluetooth/000000000000484a8205faafe216@google.com/
WARNING: Unknown link reference 'Closes:', use 'Link:' instead
#83:
Closes: https://lore.kernel.org/linux-bluetooth/000000000000484a8205faafe216@google.com/
total: 0 errors, 3 warnings, 0 checks, 33 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.
/github/workspace/src/src/13230190.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.
[v4,2/4] Bluetooth: Refcnt drop must be placed last in hci_conn_unlink
WARNING: Reported-by: should be immediately followed by Link: with a URL to the report
#83:
Reported-by: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Closes: https://lore.kernel.org/linux-bluetooth/CABBYNZ+1kce8_RJrLNOXd_8=Mdpb=2bx4Nto-hFORk=qiOkoCg@mail.gmail.com/
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#84:
Closes: https://lore.kernel.org/linux-bluetooth/CABBYNZ+1kce8_RJrLNOXd_8=Mdpb=2bx4Nto-hFORk=qiOkoCg@mail.gmail.com/
WARNING: Unknown link reference 'Closes:', use 'Link:' instead
#84:
Closes: https://lore.kernel.org/linux-bluetooth/CABBYNZ+1kce8_RJrLNOXd_8=Mdpb=2bx4Nto-hFORk=qiOkoCg@mail.gmail.com/
total: 0 errors, 3 warnings, 0 checks, 15 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.
/github/workspace/src/src/13230188.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.
[v4,3/4] Bluetooth: Fix UAF in hci_conn_hash_flush again
WARNING: Reported-by: should be immediately followed by Link: with a URL to the report
#94:
Reported-by: syzbot+8bb72f86fc823817bc5d@syzkaller.appspotmail.com
Closes: https://lore.kernel.org/linux-bluetooth/000000000000aa920505f60d25ad@google.com/
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#95:
Closes: https://lore.kernel.org/linux-bluetooth/000000000000aa920505f60d25ad@google.com/
WARNING: Unknown link reference 'Closes:', use 'Link:' instead
#95:
Closes: https://lore.kernel.org/linux-bluetooth/000000000000aa920505f60d25ad@google.com/
total: 0 errors, 3 warnings, 0 checks, 73 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.
/github/workspace/src/src/13230191.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:
[v4,1/4] Bluetooth: Fix potential double free caused by hci_conn_unlink
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
13: B1 Line exceeds max length (88>80): "Closes: https://lore.kernel.org/linux-bluetooth/000000000000484a8205faafe216@google.com/"
[v4,2/4] Bluetooth: Refcnt drop must be placed last in hci_conn_unlink
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
13: B1 Line exceeds max length (115>80): "Closes: https://lore.kernel.org/linux-bluetooth/CABBYNZ+1kce8_RJrLNOXd_8=Mdpb=2bx4Nto-hFORk=qiOkoCg@mail.gmail.com/"
[v4,3/4] Bluetooth: Fix UAF in hci_conn_hash_flush again
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
24: B1 Line exceeds max length (88>80): "Closes: https://lore.kernel.org/linux-bluetooth/000000000000aa920505f60d25ad@google.com/"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-05-03 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 13:39 [PATCH v4 1/4] Bluetooth: Fix potential double free caused by hci_conn_unlink Ruihan Li
2023-05-03 13:39 ` [PATCH v4 2/4] Bluetooth: Refcnt drop must be placed last in hci_conn_unlink Ruihan Li
2023-05-03 13:39 ` [PATCH v4 3/4] Bluetooth: Fix UAF in hci_conn_hash_flush again Ruihan Li
2023-05-03 13:39 ` [PATCH v4 4/4] Bluetooth: Unlink CISes when LE disconnects in hci_conn_del Ruihan Li
2023-05-03 14:38 ` bluez.test.bot [this message]
2023-05-03 17:30 ` [PATCH v4 1/4] Bluetooth: Fix potential double free caused by hci_conn_unlink patchwork-bot+bluetooth
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=645271e9.050a0220.cc54e.ebee@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lrh2000@pku.edu.cn \
/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.