From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gongming Chen <chengongming1900@outlook.com>
Subject: |WARNING| pw142183 [PATCH v2] vhost: fix crash caused by accessing a freed vsocket
Date: Mon, 8 Jul 2024 04:18:40 +0200 (CEST) [thread overview]
Message-ID: <20240708021840.E9BBF128144@dpdk.org> (raw)
In-Reply-To: <TYAP286MB0649F57394FD92719A1F99D8D8DA2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/142183
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#124:
#3 0x0000000004168336 in ctrl_thread_init at lib/eal/common/eal_common_thread.c:282
total: 0 errors, 1 warnings, 146 lines checked
next prev parent reply other threads:[~2024-07-08 2:18 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TYAP286MB0649F57394FD92719A1F99D8D8DA2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-07-08 1:51 ` |SUCCESS| " qemudev
2024-07-08 1:56 ` qemudev
2024-07-08 2:18 ` checkpatch [this message]
2024-07-08 2:45 ` |SUCCESS| pw142183 [PATCH] [v2] vhost: fix crash caused by accessing dpdklab
2024-07-08 2:47 ` dpdklab
2024-07-08 2:48 ` dpdklab
2024-07-08 2:49 ` dpdklab
2024-07-08 2:52 ` dpdklab
2024-07-08 2:54 ` dpdklab
2024-07-08 2:55 ` dpdklab
2024-07-08 2:55 ` |PENDING| " dpdklab
2024-07-08 2:55 ` dpdklab
2024-07-08 2:56 ` dpdklab
2024-07-08 2:56 ` |SUCCESS| " dpdklab
2024-07-08 2:58 ` |PENDING| " dpdklab
2024-07-08 2:59 ` dpdklab
2024-07-08 3:00 ` dpdklab
2024-07-08 3:03 ` |FAILURE| pw142183 [PATCH v2] vhost: fix crash caused by accessing a freed vsocket 0-day Robot
2024-07-08 3:03 ` |PENDING| pw142183 [PATCH] [v2] vhost: fix crash caused by accessing dpdklab
2024-07-08 3:05 ` |SUCCESS| " dpdklab
2024-07-08 3:07 ` |PENDING| " dpdklab
2024-07-08 3:08 ` dpdklab
2024-07-08 3:09 ` dpdklab
2024-07-08 3:09 ` dpdklab
2024-07-08 3:10 ` dpdklab
2024-07-08 3:10 ` dpdklab
2024-07-08 3:13 ` dpdklab
2024-07-08 3:13 ` |SUCCESS| " dpdklab
2024-07-08 3:13 ` |PENDING| " dpdklab
2024-07-08 3:14 ` dpdklab
2024-07-08 3:14 ` dpdklab
2024-07-08 3:15 ` dpdklab
2024-07-08 3:16 ` dpdklab
2024-07-08 3:18 ` |FAILURE| " dpdklab
2024-07-08 3:19 ` dpdklab
2024-07-08 3:19 ` |PENDING| " dpdklab
2024-07-08 3:19 ` dpdklab
2024-07-08 3:19 ` |FAILURE| " dpdklab
2024-07-08 3:19 ` |PENDING| " dpdklab
2024-07-08 3:20 ` dpdklab
2024-07-08 3:21 ` dpdklab
2024-07-08 3:21 ` dpdklab
2024-07-08 3:24 ` |SUCCESS| " dpdklab
2024-07-08 3:26 ` |FAILURE| " dpdklab
2024-07-08 3:26 ` |PENDING| " dpdklab
2024-07-08 3:27 ` |FAILURE| " dpdklab
2024-07-08 3:29 ` dpdklab
2024-07-08 3:30 ` |SUCCESS| " dpdklab
2024-07-08 3:30 ` |FAILURE| " dpdklab
2024-07-08 3:31 ` |PENDING| " dpdklab
2024-07-08 3:34 ` dpdklab
2024-07-08 3:36 ` dpdklab
2024-07-08 3:38 ` dpdklab
2024-07-08 3:39 ` |FAILURE| " dpdklab
2024-07-08 3:41 ` |PENDING| " dpdklab
2024-07-08 3:41 ` |FAILURE| " dpdklab
2024-07-08 3:41 ` |PENDING| " dpdklab
2024-07-08 3:42 ` |FAILURE| " dpdklab
2024-07-08 3:43 ` dpdklab
2024-07-08 3:43 ` dpdklab
2024-07-08 3:44 ` dpdklab
2024-07-08 3:44 ` dpdklab
2024-07-08 3:44 ` |SUCCESS| " dpdklab
2024-07-08 3:45 ` |FAILURE| " dpdklab
2024-07-08 3:46 ` dpdklab
2024-07-08 3:47 ` dpdklab
2024-07-08 3:47 ` dpdklab
2024-07-08 3:48 ` dpdklab
2024-07-08 3:48 ` dpdklab
2024-07-08 3:50 ` dpdklab
2024-07-08 3:51 ` dpdklab
2024-07-08 3:51 ` dpdklab
2024-07-08 3:52 ` dpdklab
2024-07-08 3:53 ` dpdklab
2024-07-08 3:53 ` dpdklab
2024-07-08 3:55 ` dpdklab
2024-07-08 3:57 ` dpdklab
2024-07-08 3:57 ` dpdklab
2024-07-08 3:57 ` dpdklab
2024-07-08 3:57 ` dpdklab
2024-07-08 3:58 ` dpdklab
2024-07-08 4:01 ` |SUCCESS| " dpdklab
2024-07-08 4:27 ` |FAILURE| " dpdklab
2024-07-09 11:02 ` |SUCCESS| " dpdklab
2024-07-09 11:15 ` dpdklab
2024-07-14 0:04 ` dpdklab
2024-07-14 11:03 ` dpdklab
2024-07-14 17:34 ` dpdklab
2024-07-15 10:27 ` dpdklab
2024-07-15 10:31 ` dpdklab
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=20240708021840.E9BBF128144@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=chengongming1900@outlook.com \
--cc=test-report@dpdk.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 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).