From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw106450 [PATCH] common/cnxk: fix missing null check in IPv6 flow parsing
Date: Tue, 25 Jan 2022 00:08:53 -0500 (EST) [thread overview]
Message-ID: <20220125050853.534BF314F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/106450
_apply patch failure_
Submitter: Satheesh Paul <psatheesh@marvell.com>
Date: Tuesday, January 25 2022 04:12:48
Applied on: CommitID:8a5a91401dc23ddab1ddea3667a17a615a25077f
Apply patch set 106450 failed:
Checking patch drivers/common/cnxk/roc_npc_parse.c...
error: while searching for:
ipv6_spec = pst->pattern->spec;
lid = NPC_LID_LC;
lt = NPC_LT_LC_IP6;
rc = npc_handle_ipv6ext_attr(ipv6_spec, pst, &flags);
if (rc)
return rc;
info.len = sizeof(ipv6_spec->hdr);
break;
case ROC_NPC_ITEM_TYPE_ARP_ETH_IPV4:
error: patch failed: drivers/common/cnxk/roc_npc_parse.c:562
Applying patch drivers/common/cnxk/roc_npc_parse.c with 1 reject...
Rejected hunk #1.
diff a/drivers/common/cnxk/roc_npc_parse.c b/drivers/common/cnxk/roc_npc_parse.c (rejected hunks)
@@ -562,9 +562,11 @@ npc_parse_lc(struct npc_parse_state *pst)
ipv6_spec = pst->pattern->spec;
lid = NPC_LID_LC;
lt = NPC_LT_LC_IP6;
- rc = npc_handle_ipv6ext_attr(ipv6_spec, pst, &flags);
- if (rc)
- return rc;
+ if (ipv6_spec) {
+ rc = npc_handle_ipv6ext_attr(ipv6_spec, pst, &flags);
+ if (rc)
+ return rc;
+ }
info.len = sizeof(ipv6_spec->hdr);
break;
case ROC_NPC_ITEM_TYPE_ARP_ETH_IPV4:
https://lab.dpdk.org/results/dashboard/patchsets/20796/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-01-25 5:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220125050853.534BF314F@noxus.dpdklab.iol.unh.edu \
--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).