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: [dpdk-test-report] |WARNING| pw100987 [PATCH] [v3] app: fix buffer overrun
Date: Mon, 11 Oct 2021 16:44:07 -0400 (EDT)	[thread overview]
Message-ID: <20211011204407.CBA416D76C@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_apply patch failure_

Submitter: Przemyslaw Zegan <przemyslawx.zegan@intel.com>
Date: Monday, October 11 2021 08:04:52 
Applied on: CommitID:515d20195b17444262a5732831c0615146c7189c
Apply patch set 100987 failed:

Checking patch app/test-crypto-perf/cperf_test_vectors.c...
error: while searching for:
				return NULL;
			}

			if(options->aead_aad_sz > 12)
				options->aead_aad_sz = 12;

			memcpy(t_vec->aad.data, aad, options->aead_aad_sz);
			t_vec->aad.phys_addr = rte_malloc_virt2iova(t_vec->aad.data);

error: patch failed: app/test-crypto-perf/cperf_test_vectors.c:555
Applying patch app/test-crypto-perf/cperf_test_vectors.c with 1 reject...
Rejected hunk #1.
diff a/app/test-crypto-perf/cperf_test_vectors.c b/app/test-crypto-perf/cperf_test_vectors.c	(rejected hunks)
@@ -555,8 +555,8 @@ cperf_test_vector_get_dummy(struct cperf_options *options)
 				return NULL;
 			}
 
-			if(options->aead_aad_sz > 12)
-				options->aead_aad_sz = 12;
+			if(options->aead_aad_sz > sizeof(aad))
+				options->aead_aad_sz = sizeof(aad);
 
 			memcpy(t_vec->aad.data, aad, options->aead_aad_sz);
 			t_vec->aad.phys_addr = rte_malloc_virt2iova(t_vec->aad.data);

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2021-10-11 20:44 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=20211011204407.CBA416D76C@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).