From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D3AEF45DB9 for ; Wed, 27 Nov 2024 18:23:03 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CF9C1402DE; Wed, 27 Nov 2024 18:23:03 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id A9D6B402DE for ; Wed, 27 Nov 2024 18:23:01 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1732728181; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=7BSRBTUihISDSxzeyVUfVt6pnKYg1z92abc+3FU5u/g=; b=eXQ/cLoD43/1z+9W5orTBNXfM8QRm948QWwkV3l18TgN/YWJYJL3EPngk3OmFkwim5ISFo aVjFhDi099BUP8XNUwp6xNqX0qanf0o2mHYw6QGK0kW2hIFScHdfnFNm1eaYt1BurnDIkn zgE/bF2hPaASpMGaWQLG9zzkoiNECxU= Received: from mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-347-b1pUNofoPFmn07e0mDsg6Q-1; Wed, 27 Nov 2024 12:22:55 -0500 X-MC-Unique: b1pUNofoPFmn07e0mDsg6Q-1 X-Mimecast-MFC-AGG-ID: b1pUNofoPFmn07e0mDsg6Q Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id B545C19541A1; Wed, 27 Nov 2024 17:22:53 +0000 (UTC) Received: from rh.redhat.com (unknown [10.39.192.52]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 5E17730001A2; Wed, 27 Nov 2024 17:22:51 +0000 (UTC) From: Kevin Traynor To: Farah Smith Cc: Sriharsha Basavapatna , Kishore Padmanabha , Shahaji Bhosle , Ajit Khaparde , dpdk stable Subject: patch 'net/bnxt/tf_core: fix Thor TF EM key size check' has been queued to stable release 21.11.9 Date: Wed, 27 Nov 2024 17:18:44 +0000 Message-ID: <20241127171916.690404-97-ktraynor@redhat.com> In-Reply-To: <20241127171916.690404-1-ktraynor@redhat.com> References: <20241127171916.690404-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: rpi_pG4-1uQUROndO76QigR9XWxLV-BLPKImos4lVqQ_1732728173 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit content-type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 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 Hi, FYI, your patch has been queued to stable release 21.11.9 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 12/02/24. 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. Queued patches are on a temporary branch at: https://github.com/kevintraynor/dpdk-stable This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable/commit/ad1456b8b3174ce0e7f480bfe5d9c954f6f24f41 Thanks. Kevin --- >From ad1456b8b3174ce0e7f480bfe5d9c954f6f24f41 Mon Sep 17 00:00:00 2001 From: Farah Smith Date: Thu, 7 Nov 2024 19:22:11 +0530 Subject: [PATCH] net/bnxt/tf_core: fix Thor TF EM key size check [ upstream commit 912abed4250c792214886880fa0b93b7712fba21 ] The maximum EM key size is 640 bits for Thor. But the lookup record + the key size is 679 bits. This value must be rounded up to a 128 bit aligned number. So the size check should be 96 bytes rather than 80. This fix allows keys > 601 bits to be successfully inserted. Fixes: 539931eab3a5 ("net/bnxt: support EM with FKB") Signed-off-by: Farah Smith Signed-off-by: Sriharsha Basavapatna Reviewed-by: Farah Smith Reviewed-by: Kishore Padmanabha Reviewed-by: Shahaji Bhosle Reviewed-by: Ajit Khaparde --- drivers/net/bnxt/tf_core/tf_msg.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/bnxt/tf_core/tf_msg.c b/drivers/net/bnxt/tf_core/tf_msg.c index fbc96d374c..f468de564d 100644 --- a/drivers/net/bnxt/tf_core/tf_msg.c +++ b/drivers/net/bnxt/tf_core/tf_msg.c @@ -26,5 +26,5 @@ #define TF_MSG_SET_GLOBAL_CFG_DATA_SIZE 16 #define TF_MSG_EM_INSERT_KEY_SIZE 64 -#define TF_MSG_EM_INSERT_RECORD_SIZE 80 +#define TF_MSG_EM_INSERT_RECORD_SIZE 96 #define TF_MSG_TBL_TYPE_SET_DATA_SIZE 88 -- 2.47.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2024-11-27 17:17:41.310153756 +0000 +++ 0097-net-bnxt-tf_core-fix-Thor-TF-EM-key-size-check.patch 2024-11-27 17:17:38.306269793 +0000 @@ -1 +1 @@ -From 912abed4250c792214886880fa0b93b7712fba21 Mon Sep 17 00:00:00 2001 +From ad1456b8b3174ce0e7f480bfe5d9c954f6f24f41 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 912abed4250c792214886880fa0b93b7712fba21 ] + @@ -12 +13,0 @@ -Cc: stable@dpdk.org @@ -25 +26 @@ -index 08e9783d52..dd5ea1c80e 100644 +index fbc96d374c..f468de564d 100644