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 E258AA0C41 for ; Tue, 30 Nov 2021 17:42:15 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DD46E41186; Tue, 30 Nov 2021 17:42:15 +0100 (CET) Received: from smtp-relay-internal-1.canonical.com (smtp-relay-internal-1.canonical.com [185.125.188.123]) by mails.dpdk.org (Postfix) with ESMTP id 020684118F for ; Tue, 30 Nov 2021 17:42:15 +0100 (CET) Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) (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 smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id 3E2CA4000F for ; Tue, 30 Nov 2021 16:42:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1638290534; bh=Fij9gUCLqQiF+4QYZ7/CJNw7GDa6XwLqjFsvvs45+XI=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=PtixP2GtE8WVT4iC9/h4QtjWunY6rTr4inC31WnPg4GgFeuPamWXPWwFPjD4ykQvv gLj3ujpHeAKouB6w9D8BsQYwRjS4OyrzsAXRXW/YTYEdXw9sqwOczp0ZIsKTM4rXwN BMmN+DZIf/1JH0uo8ma+JnoJZboATW/lj4LukYqN6je/qN9gBCy5IhX6dVi270zDte //d7NcOEQE0ftUz6PKLaDIpN0OZ8JVvyLoSiN/OlM40Msr6amSoFbs1ut8OTleXE76 5X5hLX+qnB8NRRVOjN8XTLowAhuZVDBUUzSS4hz381Ni2X3YY1nS5COoQg6WNzAMLW slejouS6VfaAQ== Received: by mail-ed1-f69.google.com with SMTP id p4-20020aa7d304000000b003e7ef120a37so17407819edq.16 for ; Tue, 30 Nov 2021 08:42:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Fij9gUCLqQiF+4QYZ7/CJNw7GDa6XwLqjFsvvs45+XI=; b=B+JLEL32pWjipUJKVCU/az96478OcX/N4OZj4yZUBc2sxzIQpaleJThuskkwzAaN8d c4ZVKrzhE61p3S1YvYeH8cbWZzWvw9x4/CEgny3TROwUikTNRvEDLsHrn30wQW9a5ojU 9gVW3TZrsBndoNz2KbFfBxTIG/9HxfPJmHAZJHCWKSvF1SevQARjBrtXddrMjDxKS5dr t+gXjvakbxB6XnY6wUbUXpdPHWJxRv95BWikFh9Xvre2ob8+2/wOUJlVfTF/nahPkAvN oqo0lYxGpn8Yy70phGSwirC2bXvqctzImSGn83qw9QXmWIZTUy9+gIE6LmwAtJC5iX5a nYFw== X-Gm-Message-State: AOAM530Wm2wU3gXHpQhUaByovg8X1vg5TIExS69oI8TtWv+TNm0m/2kq zsJgp2E6AHMBJLUYlcu/IbyHM9I6Dy/ia1bozc44nRxwZGXa2lmFbDWuzd2nJxm6oD36dqeVL7A RwTTg+K0bh8tYU2/TVNfpWARw X-Received: by 2002:a17:907:1626:: with SMTP id hb38mr175561ejc.481.1638290533298; Tue, 30 Nov 2021 08:42:13 -0800 (PST) X-Google-Smtp-Source: ABdhPJypcRhsN5Gf/thDL7m0d8YzEAUE08uvKpaAV2Wyl3HXfhXk0fN1wwMP0xLR81FsEoS438CqjA== X-Received: by 2002:a17:907:1626:: with SMTP id hb38mr175545ejc.481.1638290533161; Tue, 30 Nov 2021 08:42:13 -0800 (PST) Received: from localhost.localdomain ([2001:67c:1560:8007::aac:c4ad]) by smtp.gmail.com with ESMTPSA id q17sm11839723edd.10.2021.11.30.08.42.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 30 Nov 2021 08:42:12 -0800 (PST) From: christian.ehrhardt@canonical.com To: Arek Kusztal Cc: Fan Zhang , dpdk stable Subject: patch 'crypto/qat: fix status in RSA decryption' has been queued to stable release 19.11.11 Date: Tue, 30 Nov 2021 17:35:22 +0100 Message-Id: <20211130163605.2460997-118-christian.ehrhardt@canonical.com> X-Mailer: git-send-email 2.34.0 In-Reply-To: <20211130163605.2460997-1-christian.ehrhardt@canonical.com> References: <20211130163605.2460997-1-christian.ehrhardt@canonical.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 19.11.11 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before December 10th 2021. 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/cpaelzer/dpdk-stable-queue This queued commit can be viewed at: https://github.com/cpaelzer/dpdk-stable-queue/commit/5fd855c5ddbbcaf4618a324e51f830ccb3099449 Thanks. Christian Ehrhardt --- >From 5fd855c5ddbbcaf4618a324e51f830ccb3099449 Mon Sep 17 00:00:00 2001 From: Arek Kusztal Date: Thu, 21 Oct 2021 11:05:43 +0100 Subject: [PATCH] crypto/qat: fix status in RSA decryption [ upstream commit 0a9e63940337f9de9d07080b63160b5e89ea1425 ] This commit fixes not set crypto op status when decrypting with RSA algorithm. Fixes: e2c5f4ea994c ("crypto/qat: support RSA in asym") Signed-off-by: Arek Kusztal Acked-by: Fan Zhang --- drivers/crypto/qat/qat_asym.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/crypto/qat/qat_asym.c b/drivers/crypto/qat/qat_asym.c index 85973812a8..983c639d68 100644 --- a/drivers/crypto/qat/qat_asym.c +++ b/drivers/crypto/qat/qat_asym.c @@ -629,6 +629,8 @@ static void qat_asym_collect_response(struct rte_crypto_op *rx_op, rte_memcpy(rsa_result, cookie->output_array[0], alg_size_in_bytes); + rx_op->status = + RTE_CRYPTO_OP_STATUS_SUCCESS; break; default: QAT_LOG(ERR, "Padding not supported"); -- 2.34.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2021-11-30 16:50:12.888522627 +0100 +++ 0118-crypto-qat-fix-status-in-RSA-decryption.patch 2021-11-30 16:50:05.942874646 +0100 @@ -1 +1 @@ -From 0a9e63940337f9de9d07080b63160b5e89ea1425 Mon Sep 17 00:00:00 2001 +From 5fd855c5ddbbcaf4618a324e51f830ccb3099449 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 0a9e63940337f9de9d07080b63160b5e89ea1425 ] + @@ -10 +11,0 @@ -Cc: stable@dpdk.org