From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw127732 [PATCH] ring name length simplification in ipsec_mb_qp_create_processed_ops_ring
Date: Sun, 11 Jun 2023 10:53:32 -0700 (PDT) [thread overview]
Message-ID: <64860a1c.170a0220.c09e3.ac1fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/127732
_apply patch failure_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, May 30 2023 23:34:57
Applied on: CommitID:c9df59bcc9bec67783de98486879594e52bdc418
Apply patch set 127732 failed:
Checking patch drivers/crypto/ipsec_mb/ipsec_mb_ops.c...
error: while searching for:
struct ipsec_mb_qp *qp, unsigned int ring_size, int socket_id)
{
struct rte_ring *r;
char ring_name[RTE_CRYPTODEV_NAME_MAX_LEN];
unsigned int n = rte_strlcpy(ring_name, qp->name, sizeof(ring_name));
if (n >= sizeof(ring_name))
return NULL;
r = rte_ring_lookup(ring_name);
if (r) {
error: patch failed: drivers/crypto/ipsec_mb/ipsec_mb_ops.c:185
Applying patch drivers/crypto/ipsec_mb/ipsec_mb_ops.c with 1 reject...
Rejected hunk #1.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/drivers/crypto/ipsec_mb/ipsec_mb_ops.c b/drivers/crypto/ipsec_mb/ipsec_mb_ops.c (rejected hunks)
@@ -185,12 +185,7 @@ static struct rte_ring
struct ipsec_mb_qp *qp, unsigned int ring_size, int socket_id)
{
struct rte_ring *r;
- char ring_name[RTE_CRYPTODEV_NAME_MAX_LEN];
-
- unsigned int n = rte_strlcpy(ring_name, qp->name, sizeof(ring_name));
-
- if (n >= sizeof(ring_name))
- return NULL;
+ const char *ring_name = qp->name;
r = rte_ring_lookup(ring_name);
if (r) {
https://lab.dpdk.org/results/dashboard/patchsets/26457/
UNH-IOL DPDK Community Lab
next reply other threads:[~2023-06-11 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 17:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-11 18:22 dpdklab
2023-06-11 18:07 dpdklab
2023-06-09 22:58 dpdklab
2023-05-30 23:50 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=64860a1c.170a0220.c09e3.ac1fSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).