Message ID | cover.1677608527.git.noodles@earth.li |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:5915:0:0:0:0:0 with SMTP id v21csp3185495wrd; Tue, 28 Feb 2023 10:39:59 -0800 (PST) X-Google-Smtp-Source: AK7set92+El21q+k4bw94061geet4814VGf/2l5xK75ik7tH3gx6ATMiVf0GsTOzCUQSY7p2Bc8S X-Received: by 2002:a17:907:7759:b0:8b1:76dd:f5f6 with SMTP id kx25-20020a170907775900b008b176ddf5f6mr4252161ejc.50.1677609599567; Tue, 28 Feb 2023 10:39:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1677609599; cv=none; d=google.com; s=arc-20160816; b=KAnxbxILyopuGUyCgHhQ1gcVNFHOk+MvfSghY7gSOiGnJKyL3a5yK6okZpCixN4JgF x0YeUkFG+gvKMdOidOOvwbRu3WlmUFxC+cp47yLqyn5qMZJy7htE7pp6w/ta5xj13l/T LSQ5hype/pTnic3ytIYWAAfO+iSPzSxSzQeoiEVb1j52amTLv3jQ8i8s8Dd3SgEdmYsO PvTuqGhnYXvpMKRKJrEZyM9XYazWO5ZpwG06eUNhwPcyNWdeq6K01WU1AeX814XuH2Qb DcVZ2+elteeIuabFceK6aOmsGnRZ0/EoBZxaR28HfLli9WMAm6xV4eKJiZBrSKQOiw0s +D1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=cB76pDp0L9mcBCeH4RiYfMUhvVaaA8YDQDxOHX56BVk=; b=b56AooTTbMNBY36kHZgkUCSa3i6mc1UevGjYIxs+QhI2lc3iiCw2qMCbxCESfz4wAj UYFm6X50n1KGqhkvELTGx29ytaKhPjqY5gPQ3gjj1hX8fKC37QImGu7oIubrLsGFuUol sx6LU2qhiPwJ2Iqr/GMeQHRzy/BMkO14y1ueViUTPX55Maih0bv9WZKPHVZNI7VSajFR /4H6jnZx8WPnzeey5YcxEYwEc8OSGzg4UE7l9C9eY+bdCiV3jgiz4QPMPoJ6BIQRZCUK 0mhdIQl7pFWi04hBSx2QKYArM88BPyy4DPc8VUjcUYxnBzQ0AmmOIQwGweLWa02/WYpN jFJw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@earth.li header.s=the header.b=lYWJatWt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q6-20020a170906144600b008deaca3a01csi11911930ejc.221.2023.02.28.10.39.37; Tue, 28 Feb 2023 10:39:59 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=fail header.i=@earth.li header.s=the header.b=lYWJatWt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229684AbjB1S2h (ORCPT <rfc822;brysonjbanks@gmail.com> + 99 others); Tue, 28 Feb 2023 13:28:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33604 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229534AbjB1S2g (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 28 Feb 2023 13:28:36 -0500 Received: from the.earth.li (the.earth.li [IPv6:2a00:1098:86:4d:c0ff:ee:15:900d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A963D13521; Tue, 28 Feb 2023 10:28:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=earth.li; s=the; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject: Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=cB76pDp0L9mcBCeH4RiYfMUhvVaaA8YDQDxOHX56BVk=; b=lYWJatWtQcxNNhvIQ9pivEuRZx XVr5JDPdI1CFtaTX6Ti93x80HGjOZ4HDh0XcfL5sB/DEhtLAsTierRMvZjSA7orhFXGqp5TzI2kUt wI9p7aIh0kxKRNRXA5i02jXzt6sMUEtQ5emwAMfRTJNDJKgyeQgVL4j85whLxjtPblhUUZye1ojfu Emozq2UoHDkL7mSTAaB9KK4ulb9cCQdHjXFaBQbtsCIvl6P7HFnN3k9z0bXEKbrbhidr4KgRlFrcX gyc5C6kradb3fm60xGnaL5t/thIfEKGC6gKjlf6LyDQVP6tNWiKA5T7uYLidpZURPtecrMmZ9GnQA zmzcafCQ==; Received: from [2001:4d48:ad59:1403::17ca] (helo=earth.li) by the.earth.li with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <noodles@earth.li>) id 1pX4iB-008oRc-Gi; Tue, 28 Feb 2023 18:28:27 +0000 Date: Tue, 28 Feb 2023 18:28:23 +0000 From: Jonathan McDowell <noodles@earth.li> To: Antoine Tenart <atenart@kernel.org>, Herbert Xu <herbert@gondor.apana.org.au>, "David S. Miller" <davem@davemloft.net> Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 0/2] crypto: inside-secure: Handle load errors better Message-ID: <cover.1677608527.git.noodles@earth.li> References: <Y/fkOF31BTQVocSe@sevai.o362.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <Y/fkOF31BTQVocSe@sevai.o362.us> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1758663852002361084?= X-GMAIL-MSGID: =?utf-8?q?1759101163502388036?= |
Series |
crypto: inside-secure: Handle load errors better
|
|
Message
Jonathan McDowell
Feb. 28, 2023, 6:28 p.m. UTC
2 minor patches to improve the error handling of the safexcel driver when it fails to load. Firstly, make it clear when the reason for a load failure is because the firmware is not available. Secondly, ensure we clean up the ring workqueues / IRQ affinity settings to avoid a kernel warning when the driver fails to load. v2: - Expand error clean up to cover ring initialisation failures Jonathan McDowell (2): crypto: inside-secure: Raise firmware load failure message to error crypto: inside-secure - Cleanup ring IRQ workqueues on load failure drivers/crypto/inside-secure/safexcel.c | 39 ++++++++++++++++++------- 1 file changed, 28 insertions(+), 11 deletions(-)
Comments
On Tue, Feb 28, 2023 at 06:28:23PM +0000, Jonathan McDowell wrote: > 2 minor patches to improve the error handling of the safexcel driver > when it fails to load. > > Firstly, make it clear when the reason for a load failure is because the > firmware is not available. > > Secondly, ensure we clean up the ring workqueues / IRQ affinity settings > to avoid a kernel warning when the driver fails to load. > > v2: > - Expand error clean up to cover ring initialisation failures > > Jonathan McDowell (2): > crypto: inside-secure: Raise firmware load failure message to error > crypto: inside-secure - Cleanup ring IRQ workqueues on load failure > > drivers/crypto/inside-secure/safexcel.c | 39 ++++++++++++++++++------- > 1 file changed, 28 insertions(+), 11 deletions(-) > > -- > 2.39.2 All applied. Thanks.