DPDK patches and discussions
 help / color / mirror / Atom feed
From: Archana Muniganti <marchana@marvell.com>
To: <dev@dpdk.org>, <gakhil@marvell.com>
Cc: Archana Muniganti <marchana@marvell.com>,
	<roy.fan.zhang@intel.com>, <brian.dooley@intel.com>,
	<gmuthukrishn@marvell.com>, <anoobj@marvell.com>
Subject: [PATCH v1] examples/fips_validation: fix print for zero length payload
Date: Thu, 30 Jun 2022 16:51:23 +0530	[thread overview]
Message-ID: <20220630112124.4161715-1-marchana@marvell.com> (raw)

NIST GCM decrypt result vectors expects to have following print
for zero length payload instead of having no print.
"pt" = ""

Fixes: b09aac2d6e2b ("examples/fips_validation: add JSON to GCM test")

Signed-off-by: Archana Muniganti <marchana@marvell.com>
---
 examples/fips_validation/fips_validation_gcm.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/examples/fips_validation/fips_validation_gcm.c b/examples/fips_validation/fips_validation_gcm.c
index 28ef04c817..6b3d158629 100644
--- a/examples/fips_validation/fips_validation_gcm.c
+++ b/examples/fips_validation/fips_validation_gcm.c
@@ -327,6 +327,9 @@ parse_test_gcm_json_writeback(struct fips_val *val)
 				writeback_hex_str("", info.one_line_text, &tmp_val);
 				json_object_set_new(json_info.json_write_case, PT_JSON_STR,
 					json_string(info.one_line_text));
+			} else {
+				json_object_set_new(json_info.json_write_case, PT_JSON_STR,
+					json_string(""));
 			}
 		} else {
 			json_object_set_new(json_info.json_write_case, "testPassed", json_false());
-- 
2.25.1


             reply	other threads:[~2022-06-30 11:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 11:21 Archana Muniganti [this message]
2022-07-01 19:13 ` Akhil Goyal

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=20220630112124.4161715-1-marchana@marvell.com \
    --to=marchana@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=gmuthukrishn@marvell.com \
    --cc=roy.fan.zhang@intel.com \
    /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).