Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp3454763ybx; Fri, 8 Nov 2019 21:03:52 -0800 (PST) X-Google-Smtp-Source: APXvYqxl1thssXnjOMTVHkuLy45YnFZGBi9qgnir0vgTj6emfsIikvWiSh+sHAcTlbFS0sJ1nwMo X-Received: by 2002:a17:907:2070:: with SMTP id qp16mr12422370ejb.115.1573275832574; Fri, 08 Nov 2019 21:03:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573275832; cv=none; d=google.com; s=arc-20160816; b=fOTkoLLYnJx/8AN2XBAhlY96NsHjqKtNZyTXVM9rRtyZ2F53iJKsNrN/sMRsozcL+z Fiwq7CV69mQIKLQ9y5XYfXl6DgHKMK286d5zgmH6T+MK++vPCyDqj92ubA1CvUD7XHOO YJifIE4XzAXurO/w0FjktvCNrWG2+k95fo6mfUUqab9COUWAEXMtZO21yV0nDfZlUl7x e4r8sl52vtTeAxHeC45ByRLHwZxijackKy14G0BEoksIuiyaQppXvPDcfmAT+QiLASxj i4S03cTyITXRMbKXaNVI4Xp4W8/FyWcNu1DPYHjI2itOnQYMYaTgLL90bblK4fSGk3t4 KSXg== 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:to :from:date; bh=YFpF/KQoTyR1JWNL7ltZ4rsKK35I4ngQXahkDCfLpxA=; b=dmLi++YbB2bPdi2ijlbE8r+Xh0IKOG83jluwJFhsMaOeZxFw0UGFbc2OABYDq9qj2c sSfg4f5Rm2zLAUBt7YEcifj3YNeRcYDrBgRH+FwXv4bLl6AdEvPINzEqA/KwhLJeoxQc PpmBL0+KcC5CD7ESrzOqiUho7WygehxB3e6ioamQXaRqTTlTJ1XcmMonUcwx+aXMFz6q fUfLt4eI7X9dBVYDwveukffOmiqK3gdPW5rVdAHAdchaB0JRiS4KVCXZDs94VjGpuJci EhLmlqm1Lv5ZvSp9h/fEqBBu8gcMkAqpPsYXwz91Vg8hFU6oHBPTbDieZqiCF9c/aLMY jqvA== 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 c10si5903947eda.284.2019.11.08.21.03.01; Fri, 08 Nov 2019 21:03:52 -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 S1725827AbfKIFBY (ORCPT + 99 others); Sat, 9 Nov 2019 00:01:24 -0500 Received: from helcar.hmeau.com ([216.24.177.18]:33704 "EHLO deadmen.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725788AbfKIFBY (ORCPT ); Sat, 9 Nov 2019 00:01:24 -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 1iTIs5-0006nb-Un; Sat, 09 Nov 2019 13:01:14 +0800 Received: from herbert by gondobar with local (Exim 4.89) (envelope-from ) id 1iTIs0-00083U-GN; Sat, 09 Nov 2019 13:01:08 +0800 Date: Sat, 9 Nov 2019 13:01:08 +0800 From: Herbert Xu To: Tero Kristo , Gilad Ben-Yossef , David Miller , Linux Crypto Mailing List , Ard Biesheuvel , linux-omap@vger.kernel.org, Linux ARM Subject: Re: [PATCH 09/10] crypto: add timeout to crypto_wait_req Message-ID: <20191109050108.mcykgg2izb7htrek@gondor.apana.org.au> References: <20191017122549.4634-1-t-kristo@ti.com> <20191017122549.4634-10-t-kristo@ti.com> <076f0bc6-ad04-9543-db02-d7c7060db036@ti.com> <20191108022759.GB1140@sol.localdomain> <20191108091608.i5fxt2vu2nwrybgn@gondor.apana.org.au> <2ab94492-21e4-fbe0-41eb-e12b02511d7c@ti.com> <20191109022749.GB9739@sol.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191109022749.GB9739@sol.localdomain> 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 Fri, Nov 08, 2019 at 06:27:49PM -0800, Eric Biggers wrote: > > I don't see how making crypto_wait_req killable would be any better than adding > a timeout, since in both cases the crypto operation would still be proceeding in > the background while things are being freed. Right, you would need to modify the caller to actually distinguish between the killed case vs. actual completion. > Would it help if the crypto self-tests printed a pr_debug() message when > starting each test vector? These wouldn't be shown by default, but it would be > possible to enable them using dynamic-debug or by adding '#define DEBUG' to the > top of the source file. This should be simpler to implement. Thanks, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt