From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, cascardo@igalia.com
Subject: RE: Bluetooth: btmtk: avoid UAF in btmtk_process_coredump
Date: Wed, 31 Jul 2024 12:33:36 -0700 (PDT) [thread overview]
Message-ID: <66aa9190.c80a0220.ffa5e.5a57@mx.google.com> (raw)
In-Reply-To: <20240731190330.1619718-1-cascardo@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 3322 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=875598
---Test result---
Test Summary:
CheckPatch FAIL 0.94 seconds
GitLint FAIL 0.50 seconds
SubjectPrefix PASS 0.83 seconds
BuildKernel PASS 30.40 seconds
CheckAllWarning PASS 45.30 seconds
CheckSparse PASS 38.73 seconds
CheckSmatch PASS 104.59 seconds
BuildKernel32 PASS 29.56 seconds
TestRunnerSetup PASS 539.78 seconds
TestRunner_l2cap-tester PASS 20.46 seconds
TestRunner_iso-tester PASS 41.69 seconds
TestRunner_bnep-tester PASS 5.08 seconds
TestRunner_mgmt-tester PASS 119.77 seconds
TestRunner_rfcomm-tester PASS 7.79 seconds
TestRunner_sco-tester PASS 15.28 seconds
TestRunner_ioctl-tester PASS 8.33 seconds
TestRunner_mesh-tester PASS 6.25 seconds
TestRunner_smp-tester PASS 7.19 seconds
TestRunner_userchan-tester PASS 5.36 seconds
IncrementalBuild PASS 28.58 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: btmtk: avoid UAF in btmtk_process_coredump
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#81:
CPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G U 6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688c
total: 0 errors, 1 warnings, 37 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/13749065.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: btmtk: avoid UAF in btmtk_process_coredump
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
10: B1 Line exceeds max length (140>80): "CPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G U 6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688c"
11: B1 Line exceeds max length (90>80): "Hardware name: Google Yaviks_Ufs/Yaviks_Ufs, BIOS Google_Yaviks_Ufs.15217.552.0 05/07/2024"
18: B1 Line exceeds max length (84>80): " btmtk_process_coredump+0x2a7/0x2d0 [btmtk 03edd567dd71a65958807c95a65db31d433e1d01]"
58: B1 Line exceeds max length (90>80): "page:00000000a174ba93 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x33cfa"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-07-31 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 19:03 [PATCH] Bluetooth: btmtk: avoid UAF in btmtk_process_coredump Thadeu Lima de Souza Cascardo
2024-07-31 19:33 ` bluez.test.bot [this message]
2024-08-22 9:57 ` Thadeu Lima de Souza Cascardo
2024-09-02 3:39 ` Chris Lu (陸稚泓)
2024-12-10 19:36 ` [PATCH Resend] " Thadeu Lima de Souza Cascardo
2024-12-10 20:34 ` [Resend] " bluez.test.bot
2024-12-11 16:50 ` [PATCH Resend] " patchwork-bot+bluetooth
2024-12-12 10:03 ` AngeloGioacchino Del Regno
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=66aa9190.c80a0220.ffa5e.5a57@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=cascardo@igalia.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.