automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw115945 [PATCH] net/ice: avoid out-of-bound access
Date: Mon,  5 Sep 2022 22:52:01 -0400 (EDT)	[thread overview]
Message-ID: <20220906025201.2A2086D509@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/115945

_apply patch failure_

Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Tuesday, September 06 2022 02:28:59 
Applied on: CommitID:4aee6110bb10b0225fa9562f2e48af233a9058a1
Apply patch set 115945 failed:

Checking patch drivers/net/ice/ice_switch_filter.c...
error: while searching for:
		case RTE_FLOW_ACTION_TYPE_REPRESENTED_PORT:
			rule_info->sw_act.fltr_act = ICE_FWD_TO_VSI;
			act_ethdev = action->conf;
			repr_dev = &rte_eth_devices[act_ethdev->port_id];

			if (!repr_dev->data)

error: patch failed: drivers/net/ice/ice_switch_filter.c:1631
Applying patch drivers/net/ice/ice_switch_filter.c with 1 reject...
Rejected hunk #1.
diff a/drivers/net/ice/ice_switch_filter.c b/drivers/net/ice/ice_switch_filter.c	(rejected hunks)
@@ -1631,6 +1631,10 @@ ice_switch_parse_dcf_action(struct ice_dcf_adapter *ad,
 		case RTE_FLOW_ACTION_TYPE_REPRESENTED_PORT:
 			rule_info->sw_act.fltr_act = ICE_FWD_TO_VSI;
 			act_ethdev = action->conf;
+
+			if (!rte_eth_dev_is_valid_port(act_ethdev->port_id))
+				goto invalid;
+
 			repr_dev = &rte_eth_devices[act_ethdev->port_id];
 
 			if (!repr_dev->data)

https://lab.dpdk.org/results/dashboard/patchsets/23416/

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2022-09-06  2:52 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=20220906025201.2A2086D509@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).