From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw123898 [PATCH] net/sfc: enforce fate action in transfer flow rules
Date: Tue, 14 Feb 2023 08:28:55 -0500 (EST) [thread overview]
Message-ID: <20230214132855.D276C456@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/123898
_apply patch failure_
Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Tuesday, February 14 2023 13:12:47
Applied on: CommitID:39d469a7eb4f157923be73aea0b0cc1015860ca7
Apply patch set 123898 failed:
Checking patch drivers/net/sfc/sfc_mae.c...
error: while searching for:
SFC_ASSERT(B_FALSE);
}
spec_mae->action_set = sfc_mae_action_set_attach(sa, &ctx);
if (spec_mae->action_set != NULL) {
sfc_mae_mac_addr_del(sa, ctx.src_mac);
error: patch failed: drivers/net/sfc/sfc_mae.c:3910
Hunk #2 succeeded at 3924 (offset -17 lines).
Applying patch drivers/net/sfc/sfc_mae.c with 1 reject...
Rejected hunk #1.
Hunk #2 applied cleanly.
diff a/drivers/net/sfc/sfc_mae.c b/drivers/net/sfc/sfc_mae.c (rejected hunks)
@@ -3910,6 +3910,21 @@ sfc_mae_rule_parse_actions(struct sfc_adapter *sa,
SFC_ASSERT(B_FALSE);
}
+ /*
+ * A DPDK flow entry must specify a fate action, which the parser
+ * converts into a DELIVER action in a libefx action set. An
+ * attempt to replace the action in the action set should
+ * fail. If it succeeds then report an error, as the
+ * parsed flow entry did not contain a fate action.
+ */
+ rc = efx_mae_action_set_populate_drop(ctx.spec);
+ if (rc == 0) {
+ rc = rte_flow_error_set(error, EINVAL,
+ RTE_FLOW_ERROR_TYPE_ACTION, NULL,
+ "no fate action found");
+ goto fail_check_fate_action;
+ }
+
spec_mae->action_set = sfc_mae_action_set_attach(sa, &ctx);
if (spec_mae->action_set != NULL) {
sfc_mae_mac_addr_del(sa, ctx.src_mac);
https://lab.dpdk.org/results/dashboard/patchsets/25392/
UNH-IOL DPDK Community Lab
next reply other threads:[~2023-02-14 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 13:28 dpdklab [this message]
[not found] <20230214131247.7189-1-ivan.malov@arknetworks.am>
2023-02-14 13:03 ` qemudev
2023-02-14 13:13 ` checkpatch
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=20230214132855.D276C456@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).