From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id E5D8FA055A for ; Thu, 27 Feb 2020 10:34:14 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8E9E91BFCD; Thu, 27 Feb 2020 10:34:14 +0100 (CET) Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) by dpdk.org (Postfix) with ESMTP id 1BF791F1C for ; Thu, 27 Feb 2020 10:34:13 +0100 (CET) Received: by mail-wr1-f49.google.com with SMTP id u6so2450256wrt.0 for ; Thu, 27 Feb 2020 01:34:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=WaRcWh8yv0HQftPwPF85Oj18Ay2PvELTji1pJN/8UVE=; b=vQ308UfWm8qZ2SyruKUa7zZKjSZgUL6C1vodQW/9uuQgj7Pu3/EVjeGZIdxsJDuzL9 BAX2Us6p77mYmam8MeIxAKne5QikriSTzgNHshlJ16Yptz+lA2NBdlUxJ/BIPJYTu7YF auBKO3SQcrlWnrqXS8+qsv5tIDH43i/eGi8NHkKQ+/fsYTAehdnz9Xc82bwggTbKtg+o G41uZv5/q0W4TJpl18VQPZMFfwcCjRFD/DAX/SqmhiMXeJc5MiMQGVWvTOXB5/EUeYo7 GtA7z2zYnib+LPdTVKffOjR05SwEr9M67pqMopnLhGK4AswwjIs72L9EAPv/vAlMsm6l IaEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=WaRcWh8yv0HQftPwPF85Oj18Ay2PvELTji1pJN/8UVE=; b=DyLfKJw8BIeEkIyk2Fti0zYchYN8o8g3jHjJZEEOYspH4OhjwoWQAGwDZ8UB2/tKKm r4BYebt7Ip+rWEullKISejpzflYC4wlQ/8yx7sGhoznV/EXM3PUusicsMaVXINRcrxBw tRTLqW2ZZ15r2dAFZmEUS5kLki0Ncn6jkQE/L4PpLwpjRmGjVp87UUA3pREeHgc6Pk0z +V0JAOdKP+nRmdWami+QyYphGhtlLlMM0l5PeympSnZdz09kLcZk6NU+BZs9RdHvAQG9 +8UXWBsGRBoc0dKfnD0rDFOXKUCzemoWvsChylo/UuJUBHXF3Pleo0UxJM4lW38I3fOE dgCw== X-Gm-Message-State: APjAAAU+cO7X74qFdDCnr/dv/U0c+lfeBmVBpafbDdyGmyeOD9nqFv8O SdGNWb3kp/qH5ye8sghEgqc= X-Google-Smtp-Source: APXvYqyEsFNGWv8jdM0Vo0H5oub+dHKJugUexxtCED914VvQrGp+stETWi+dIHJ/DpsK9N7BVfAyGg== X-Received: by 2002:a5d:610a:: with SMTP id v10mr3676249wrt.267.1582796052843; Thu, 27 Feb 2020 01:34:12 -0800 (PST) Received: from localhost ([88.98.246.218]) by smtp.gmail.com with ESMTPSA id c74sm7274277wmd.26.2020.02.27.01.34.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 27 Feb 2020 01:34:12 -0800 (PST) From: luca.boccassi@gmail.com To: Anoob Joseph Cc: Akhil Goyal , dpdk stable Date: Thu, 27 Feb 2020 09:33:23 +0000 Message-Id: <20200227093402.17690-3-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20200227093402.17690-1-luca.boccassi@gmail.com> References: <20200217174546.25334-54-luca.boccassi@gmail.com> <20200227093402.17690-1-luca.boccassi@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-stable] patch 'examples/fips_validation: fix string token for CT length' has been queued to stable release 19.11.1 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to stable release 19.11.1 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 02/29/20. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Thanks. Luca Boccassi --- >From ea800a57d6442594a91f23c80e829ab0fb6cde09 Mon Sep 17 00:00:00 2001 From: Anoob Joseph Date: Tue, 18 Feb 2020 16:01:12 +0530 Subject: [PATCH] examples/fips_validation: fix string token for CT length [ upstream commit b1ea86a07cbce6d5b0a9b05a4e0c0fbbe56ad20d ] The NIST test vectors use the string 'PTlen' to denote text lengths in case of encrypt & decrypt operations. So the same string needs to be used while parsing PT and CT. Fixes: 2adb3b4e7e54 ("examples/fips_validation: fix AES-GCM cipher length parsing") Signed-off-by: Anoob Joseph Acked-by: Akhil Goyal --- examples/fips_validation/fips_validation_gcm.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/examples/fips_validation/fips_validation_gcm.c b/examples/fips_validation/fips_validation_gcm.c index bc2d37dcbf..47576e9a38 100644 --- a/examples/fips_validation/fips_validation_gcm.c +++ b/examples/fips_validation/fips_validation_gcm.c @@ -19,7 +19,6 @@ #define PTLEN_STR "PTlen = " #define AADLEN_STR "AADlen = " #define TAGLEN_STR "Taglen = " -#define CTLEN_STR "CTlen = " #define COUNT_STR "Count = " #define KEY_STR "Key = " @@ -47,7 +46,10 @@ struct fips_test_callback gcm_interim_vectors[] = { {KEYLEN_STR, parser_read_uint32_bit_val, &vec.aead.key}, {IVLEN_STR, parser_read_uint32_bit_val, &vec.iv}, {PTLEN_STR, parser_read_uint32_bit_val, &vec.pt}, - {CTLEN_STR, parser_read_uint32_bit_val, &vec.ct}, + {PTLEN_STR, parser_read_uint32_bit_val, &vec.ct}, + /**< The NIST test vectors use 'PTlen' to denote input text + * length in case of decrypt & encrypt operations. + */ {AADLEN_STR, parser_read_uint32_bit_val, &vec.aead.aad}, {TAGLEN_STR, parser_read_uint32_bit_val, &vec.aead.digest}, -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2020-02-27 09:31:55.944088518 +0000 +++ 0003-examples-fips_validation-fix-string-token-for-CT-len.patch 2020-02-27 09:31:55.631945112 +0000 @@ -1,8 +1,10 @@ -From b1ea86a07cbce6d5b0a9b05a4e0c0fbbe56ad20d Mon Sep 17 00:00:00 2001 +From ea800a57d6442594a91f23c80e829ab0fb6cde09 Mon Sep 17 00:00:00 2001 From: Anoob Joseph Date: Tue, 18 Feb 2020 16:01:12 +0530 Subject: [PATCH] examples/fips_validation: fix string token for CT length +[ upstream commit b1ea86a07cbce6d5b0a9b05a4e0c0fbbe56ad20d ] + The NIST test vectors use the string 'PTlen' to denote text lengths in case of encrypt & decrypt operations. So the same string needs to be used while parsing PT and CT.