From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 2B780A00E6 for ; Tue, 16 Apr 2019 16:49:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D5C371B4D8; Tue, 16 Apr 2019 16:49:34 +0200 (CEST) Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130045.outbound.protection.outlook.com [40.107.13.45]) by dpdk.org (Postfix) with ESMTP id 87AFF1B4D2 for ; Tue, 16 Apr 2019 16:49:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nxp.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=sa0qGlYYeE1rCVhvySxvBq8UJK8s3kTH/u9NwG+xI6k=; b=DjaX2RKKR8A+WImnBtz63BLfuEBOwTUD7oInidWrf4bhZWZQeMbcXW1XPR1e/VTyfHlzEjp7bgVD8n1edB9+Bzpe2Crweq3ADnaoY1yoQukWPnxp4oC0m7AZdM5Y+s0uyTThI2NUnNo/MBaQt6MNxDDW+a56B6EI35bsrLGNPcI= Received: from VI1PR04MB4893.eurprd04.prod.outlook.com (20.177.49.154) by VI1PR04MB6141.eurprd04.prod.outlook.com (20.179.27.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.17; Tue, 16 Apr 2019 14:49:31 +0000 Received: from VI1PR04MB4893.eurprd04.prod.outlook.com ([fe80::98b0:84a6:1c08:57c7]) by VI1PR04MB4893.eurprd04.prod.outlook.com ([fe80::98b0:84a6:1c08:57c7%3]) with mapi id 15.20.1792.018; Tue, 16 Apr 2019 14:49:31 +0000 From: Akhil Goyal To: Marko Kovacevic , "dev@dpdk.org" CC: "john.mcnamara@intel.com" , "xinfengx.zhao@intel.com" , "damianx.nowak@intel.com" Thread-Topic: [PATCH v2 1/3] examples/fips: fix hmac test failure Thread-Index: AdT0Y5iXby70mWabSVmcDFFu7Sx4lQ== Date: Tue, 16 Apr 2019 14:49:31 +0000 Message-ID: Accept-Language: en-IN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=akhil.goyal@nxp.com; x-originating-ip: [92.120.1.65] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 71fa2039-00de-4040-f48b-08d6c27abc1a x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600140)(711020)(4605104)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:VI1PR04MB6141; x-ms-traffictypediagnostic: VI1PR04MB6141: x-microsoft-antispam-prvs: x-forefront-prvs: 000947967F x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(396003)(376002)(136003)(346002)(39860400002)(366004)(199004)(189003)(52536014)(74316002)(55016002)(6246003)(486006)(53936002)(6116002)(9686003)(3846002)(5660300002)(476003)(305945005)(54906003)(110136005)(14454004)(229853002)(7736002)(33656002)(66066001)(105586002)(25786009)(44832011)(4326008)(316002)(6436002)(8936002)(81156014)(8676002)(81166006)(106356001)(102836004)(86362001)(99286004)(186003)(7696005)(2906002)(97736004)(6506007)(478600001)(14444005)(2501003)(26005)(4744005)(68736007)(256004)(71200400001)(71190400001)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR04MB6141; H:VI1PR04MB4893.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: nxp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: pRV73BPDNzZZnMVPUO9wcLMl2AmCBKU7y/8vx9aCtCK8VLKJumQIVgZhG7ESxLGASoaRIvtVBubCxrrtk0dDsmvfVFamQ8cnGJD8BiT+pCOj/CdlepvqH7/PQjolRtWXJPMGemTKDBVYdCr3WeUc3zRnCE7x6T2FW6mKXE2bwGgx5Q55cH9KrfsiIpG7VqBTGIKk4dRGsGzduAbU1NSULOxfAKGYkqhDx5hwdske8mL6mlf1rFRuESj3KAjMflbBKEuborJDw4+59G+8Tjo5uJdBEtOYoEamQnWy1FQUEGb+DJ9ky6LJDddvJpFjzpH37UXM2ekqjp9KDopKqitNXasGv/kREXXz245xzIU0iljof3rkAAvkSYfNmwLFTdBLdUg9SUHFW51r9I1dKKNCxtqCHWmKeymOsxOQyv6RhfI= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: nxp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 71fa2039-00de-4040-f48b-08d6c27abc1a X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Apr 2019 14:49:31.5904 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR04MB6141 Subject: Re: [dpdk-dev] [PATCH v2 1/3] examples/fips: fix hmac test failure X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190416144931.CVL4tNjKsImLlI-52AdVXkC8swAK_JtyC7MpJ0pD0bU@z> > Application was failing as the HMAC and > Plain SHA fips request files are similar in a > way that they both have SHA- in the top section to > determine the hash algo and hash sizes. And HMAC having the > algo in the second line but the Plain SHA in the third > meant that when the HMAC files was used once it parsed the third > line Plain SHA was set as the algo and not HMAC. >=20 > USER1: Failed to get capability for cdev 0 > USER1: Error -22: test block > [L=3D20 SHAAlg=3DSHA_2] > USER1: Error -22: Failed test /root/FIPS/HMAC/req/HMAC.req >=20 > Fixes: f4797bae0050 ("examples/fips_validation: support plain SHA") > Cc: damianx.nowak@intel.com >=20 > Signed-off-by: Marko Kovacevic > --- Series Applied to dpdk-next-crypto Thanks.