Received: by 2002:a05:7412:3784:b0:e2:908c:2ebd with SMTP id jk4csp1206459rdb; Mon, 2 Oct 2023 02:26:35 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEEm/4KEubM6lkjPfmTLopdipnwww5WHGw+08CxS1EhhbTXatmbY/a3AfCt7SaUi0f2qfhr X-Received: by 2002:a05:6808:31a:b0:3a7:6d64:aa68 with SMTP id i26-20020a056808031a00b003a76d64aa68mr11221821oie.18.1696238794816; Mon, 02 Oct 2023 02:26:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1696238794; cv=none; d=google.com; s=arc-20160816; b=NPd614TKUWmtaeTs9/Ca/C33buBcMKNbr52Ysc1pxq6cH+v5QPMYwZofOzjh6T5nJ3 hkbF9KCY7w1ODsLTYctITYSaD84MMzYfB02urHRdK6qcNBeYKWuf3JAo9X3rKtI6AYKE AuRZdhXeFkskeREnzJtLbg2tPbJvkHbmvIZ2BV8Q+7CszMiot6FedNkluXticCnPrefF XKroYWf4urxwPiL8e3eFN7esb/5kEjFne/60Frp3XMsAoRD70KfHD+Em2iwD1bHM6E83 dLcFF3zK41ESX7e3BuxdaPyx8wX+QxRyXbl04GhJm4DpbFol6xNGHCUIETNZjctakDUA YsIw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:dkim-signature; bh=XeICUbMfmTh7beF2Sq022ow9UPF6kDmSYo3jFc/ZOTU=; fh=Cal14dd6ix1C+ltZVhRzDQl8g+KXZdpFipOINgsJ0Qc=; b=C98Elv0aN0kRX6HL176SRWIQRKy0wS4NJvvmUaykuUFnEN4JTLHpoog6pyMi3jW1lL YeGnc51tnlrEB1dAUY7GPqG6Mwj0WexXs36UWaNj9Xc2hpQ+AgU+y6fcOQBlskS3Jg2y IQxq374TfVH+cOHn3wYQ0/q2bJIQRyBDy0IAA3FuEGGljwjNsVYtGKJuXItLNQ7SqtdY ovZF8SrbQG6zmu1dYjj0UcM7TeBeXxVDHxkCh2TqqMzMbl1UqbHwlbWOvNnpq01o9bB5 PIZpVRgGe9tGB9VOpPja8xFZeSlm5yhksWghBW+18nbKhGbK4nXr0i9J5wMOY6fRDIgt 8vBg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZfCcEE3W; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from groat.vger.email (groat.vger.email. [2620:137:e000::3:5]) by mx.google.com with ESMTPS id l3-20020a654c43000000b00573fc592e9dsi26824115pgr.848.2023.10.02.02.26.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Oct 2023 02:26:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZfCcEE3W; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id 8AA2080774B1; Mon, 2 Oct 2023 02:16:15 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236032AbjJBJQP (ORCPT + 99 others); Mon, 2 Oct 2023 05:16:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53128 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236036AbjJBJQO (ORCPT ); Mon, 2 Oct 2023 05:16:14 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A69A39E for ; Mon, 2 Oct 2023 02:15:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1696238126; 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: in-reply-to:in-reply-to:references:references; bh=XeICUbMfmTh7beF2Sq022ow9UPF6kDmSYo3jFc/ZOTU=; b=ZfCcEE3WGuvYx9h/2Q/9R/QZXUvd32zB7LGRew/bsRfquNwjhSGXESKAK4zsT5vVJ0Keot rYaM/hAq/0seDmCLlTcDb2Vlt0ATZNCV40M8oOJhHqcjdwsSWxbqtb4t3OTavGe2KXlQEC sCksEwvv55zm/aiiAQmczotZ38pIzk4= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-84-R-LOw29FM_GH4bd9fkwt_Q-1; Mon, 02 Oct 2023 05:15:05 -0400 X-MC-Unique: R-LOw29FM_GH4bd9fkwt_Q-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 4EEAE1C09A46; Mon, 2 Oct 2023 09:15:05 +0000 (UTC) Received: from file1-rdu.file-001.prod.rdu2.dc.redhat.com (unknown [10.11.5.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2949F40107B; Mon, 2 Oct 2023 09:15:05 +0000 (UTC) Received: by file1-rdu.file-001.prod.rdu2.dc.redhat.com (Postfix, from userid 12668) id 1E38130C0500; Mon, 2 Oct 2023 09:15:05 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by file1-rdu.file-001.prod.rdu2.dc.redhat.com (Postfix) with ESMTP id 1D4CC3FD54; Mon, 2 Oct 2023 11:15:05 +0200 (CEST) Date: Mon, 2 Oct 2023 11:15:05 +0200 (CEST) From: Mikulas Patocka To: Giovanni Cabiddu cc: Herbert Xu , "David S. Miller" , Michael Hrivnak , Eric Garver , qat-linux@intel.com, linux-crypto@vger.kernel.org, dm-devel@redhat.com Subject: Re: [PATCH v2] qat: fix deadlock in backlog processing In-Reply-To: Message-ID: <6b5cb6f-e4bb-8328-a718-f21b2575b8@redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 X-Spam-Status: No, score=2.7 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Mon, 02 Oct 2023 02:16:15 -0700 (PDT) On Fri, 29 Sep 2023, Giovanni Cabiddu wrote: > On Fri, Sep 22, 2023 at 06:34:16PM +0200, Mikulas Patocka wrote: > > > > > Also, deserves a fixes tag. > > > > "Fixes" tag is for something that worked and that was broken in some > > previous commit. > That's right. > > > A quick search through git shows that QAT backlogging was > > broken since the introduction of QAT. > The driver was moved from drivers/crypto/qat to drivers/crypto/intel/qat > that's why you see a single patch. > This fixes 386823839732 ("crypto: qat - add backlog mechanism") But before 386823839732 it also didn't work - it returned -EBUSY without queuing the request and deadlocked. > Thanks - when I proposed the rework I was thinking at a solution without > gotos. Here is a draft: Yes - it is possible to fix it this way. > ------------8<---------------- > .../intel/qat/qat_common/qat_algs_send.c | 40 ++++++++++--------- > 1 file changed, 22 insertions(+), 18 deletions(-) > > diff --git a/drivers/crypto/intel/qat/qat_common/qat_algs_send.c b/drivers/crypto/intel/qat/qat_common/qat_algs_send.c > index bb80455b3e81..18c6a233ab96 100644 > --- a/drivers/crypto/intel/qat/qat_common/qat_algs_send.c > +++ b/drivers/crypto/intel/qat/qat_common/qat_algs_send.c > @@ -40,17 +40,7 @@ void qat_alg_send_backlog(struct qat_instance_backlog *backlog) > spin_unlock_bh(&backlog->lock); > } > > -static void qat_alg_backlog_req(struct qat_alg_req *req, > - struct qat_instance_backlog *backlog) > -{ > - INIT_LIST_HEAD(&req->list); > - > - spin_lock_bh(&backlog->lock); > - list_add_tail(&req->list, &backlog->list); > - spin_unlock_bh(&backlog->lock); > -} > - > -static int qat_alg_send_message_maybacklog(struct qat_alg_req *req) > +static bool qat_alg_try_enqueue(struct qat_alg_req *req) > { > struct qat_instance_backlog *backlog = req->backlog; > struct adf_etr_ring_data *tx_ring = req->tx_ring; > @@ -58,22 +48,36 @@ static int qat_alg_send_message_maybacklog(struct qat_alg_req *req) > > /* If any request is already backlogged, then add to backlog list */ > if (!list_empty(&backlog->list)) > - goto enqueue; > + return false; > > /* If ring is nearly full, then add to backlog list */ > if (adf_ring_nearly_full(tx_ring)) > - goto enqueue; > + return false; > > /* If adding request to HW ring fails, then add to backlog list */ > if (adf_send_message(tx_ring, fw_req)) > - goto enqueue; > + return false; > > - return -EINPROGRESS; > + return true; > +} > > -enqueue: > - qat_alg_backlog_req(req, backlog); > > - return -EBUSY; > +static int qat_alg_send_message_maybacklog(struct qat_alg_req *req) > +{ > + struct qat_instance_backlog *backlog = req->backlog; > + int ret = -EINPROGRESS; > + > + if (qat_alg_try_enqueue(req)) > + return ret; > + > + spin_lock_bh(&backlog->lock); > + if (!qat_alg_try_enqueue(req)) { > + list_add_tail(&req->list, &backlog->list); > + ret = -EBUSY; > + } > + spin_unlock_bh(&backlog->lock); > + > + return ret; > } > > int qat_alg_send_message(struct qat_alg_req *req) > -- > 2.41.0 Reviwed-by: Mikulas Patocka Mikulas