Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp1112368ybc; Tue, 19 Nov 2019 14:50:51 -0800 (PST) X-Google-Smtp-Source: APXvYqypXGtr7UhMd/+/2P3nkxjTT1lTjBAoTRwGx/Y7vLjcVRoILgIaVGn0p/y5MeTMwT25iI7h X-Received: by 2002:a17:907:20b8:: with SMTP id pw24mr260344ejb.28.1574203851149; Tue, 19 Nov 2019 14:50:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574203851; cv=none; d=google.com; s=arc-20160816; b=X0rvkAVLzThqdPbNVrVMrsktSBIBaszL6I7lBLHKvLa3kUle03ZiZW6/+fHOmtuWfb sH9NdT1EEojt+WEVQdZzJsSTiqVw+8DDLH09ynl9PtRX9qkkXDEPgpJzioM5GuH8sV63 ePUZlzVaTSbh1eqYsriirfA3vKtmnEHnqoLw7Ujs8PM2Fu1ydfSz5UfORNTiJ5E2VCQO BTNyUBfPreD5QOI1CzkTMFiVkkyHWyjgvPvB5WQk6fWmJ6GlecQzLOD7wU6bmF45ZIF7 33JAZW983joe+G6kGEnOgTCAMLN8Z5v3vp45EzzFSL0OsynZ7y+JgP29sbN9xGZWuj1y SBsA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=tQnEqi+HyXp3s9CJUp5AZQ3WMfq5AgeMVNTZ4Q1ya1s=; b=D1wbV8fW+el7pt+f8D98F6P/8OHS/ywpk7XLMuBAHmI+LIixyS2IetIIsvpTvFv3Ch TLHJ9OiBs0E4HT5sF51byESTLeJAHiP8FaaAhAP8loppR2xRdYpcFF2x8ktb0XvbZMi6 4vv59QXJOt0qU7YDbMww72+19QNcJD2rGTwuBvvOU8NBejmCQOSdbk9SkVAmALuFq076 +k8mvARxn9BgpxQqc1UBqaahGZ41f417aAKHQ8EpbjKJ7tUUStV/f0pxeh5HhNytcZld LIOLBoq1TNy9f/KUoYBxpmGEJwAeN1Pz7Y8VaULnKd6N6sOezuA3r/b3QMZUTvHEoRit o2mw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b7si17215765ede.12.2019.11.19.14.50.26; Tue, 19 Nov 2019 14:50:51 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726539AbfKSWuX (ORCPT + 99 others); Tue, 19 Nov 2019 17:50:23 -0500 Received: from helcar.hmeau.com ([216.24.177.18]:50178 "EHLO deadmen.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726290AbfKSWuX (ORCPT ); Tue, 19 Nov 2019 17:50:23 -0500 Received: from gondobar.mordor.me.apana.org.au ([192.168.128.4] helo=gondobar) by deadmen.hmeau.com with esmtps (Exim 4.89 #2 (Debian)) id 1iXCKB-00018Q-9n; Wed, 20 Nov 2019 06:50:19 +0800 Received: from herbert by gondobar with local (Exim 4.89) (envelope-from ) id 1iXCKA-0000FY-0I; Wed, 20 Nov 2019 06:50:18 +0800 Date: Wed, 20 Nov 2019 06:50:17 +0800 From: Herbert Xu To: Daniel Jordan Cc: Linux Crypto Mailing List , Steffen Klassert , linux-kernel@vger.kernel.org Subject: Re: [PATCH] padata: Remove broken queue flushing Message-ID: <20191119225017.mjrak2fwa5vccazl@gondor.apana.org.au> References: <20191119051731.yev6dcsp2znjaagz@gondor.apana.org.au> <20191119192405.imfi6q4u3g2zgstc@ca-dmjordan1.us.oracle.com> <20191119215345.jr7y47b37ivshwcm@gondor.apana.org.au> <20191119224432.vr7lyoaqdzpelszo@ca-dmjordan1.us.oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191119224432.vr7lyoaqdzpelszo@ca-dmjordan1.us.oracle.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Tue, Nov 19, 2019 at 05:44:32PM -0500, Daniel Jordan wrote: > > I assume you mean the third patch you recently posted, "crypto: pcrypt - Avoid > deadlock by using per-instance padata queues". That's true, the problem is > fixed there, and the bug being present in bisection doesn't seem like enough > justification to implement something short-lived just to prevent it. Right. But as pcrypt is the only user this should still work. > Makes sense to me, though I don't see how it's enforced now in pcrypt. I'm not > an async crypto person, but wouldn't unloading the pcrypt module when there are > still outstanding async jobs break this rule? It's enforced through module reference counting. While there are any outstanding requests, there must be allocated crypto tfms. Each crypto tfm maintains a module reference count on pcrypt which prevents it from being unloaded. > Actually, I'm working on an RFC right now to add more users for padata. It > should be posted in the coming week or two, and I hope it can be part of that > discussion. OK. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt