Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp2345406imm; Thu, 21 Jun 2018 10:57:02 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJeQn0WCz9JOGEbS8kBn+W6/OJZX8+bIXVrcF/l45Byq2h0kcQMYHljCOYMVBiyYrcowgv8 X-Received: by 2002:a65:6612:: with SMTP id w18-v6mr22978345pgv.38.1529603822328; Thu, 21 Jun 2018 10:57:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529603822; cv=none; d=google.com; s=arc-20160816; b=ci7da457wpRSFEBU+8HhYfOW+am4Rf1DVqKOMmQKl3ChUlCgG0UfjozHj6oRwdCJ7V NSkiQ/cTPxRekSmnDiIYAPisGFCbBcIz0fBOJ8lnmaZPLRyKjztuaNdQhJ+ll1bAvRJ9 V5L+OJwwEao6BkZhmQNo+ZhYYL4vld7pHaFZRS0yLEqLl+Ebi6M0KV/2k7gD2OocmrWx P4tOnjAqbtgqfdMmK5hmyFgE7mNesMP1PnW4cXLywFKYdL1V/jm6OvLmsqeYucNfUWCm hEWQgxz3Y2QsswIdEYmnzJLn5LkI40xHNQ/6LDDjbaBz84evIFIxA3WfFlTxe53tehEY bUzg== 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:dkim-signature:arc-authentication-results; bh=DuO1Ofdlbp8EJhcL9UUhMWN0HhbNewTkGhy44D3euDg=; b=ikEgqNKoENd3n6qo+Tjn3fUPQZ5nVhsRTaUIVge/aehDs7KZGRy9HK1hArNq7emoWj +fRcewZXKpMvkyfuSTTBAo8ZDZq5+Hoz5wnnCg+XMoRpI7uX1dyixkaUtM8UgxAt5WQE 1Ss8+3hpQGU8hq0QtzKuyWiVwSasDNQUDv+6BaHmptvd0gv/RHoqLhQgnaaPYj9sGXCO J6zENdDavPoDwICnVh86u4woVs7R4jNdkqS4nqa5OSnFhb76nZDacKbet/sZxQ/LoqMB qWhKRZ7klL8oXqhbGGIZzMkkrTNWa28o1ttpwFskgTOvpjnF5qgzJejc+8Bageo7NnN0 fXaA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=OQropncG; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-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 o19-v6si4247720pgc.299.2018.06.21.10.56.48; Thu, 21 Jun 2018 10:57:02 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=OQropncG; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932899AbeFUR4I (ORCPT + 99 others); Thu, 21 Jun 2018 13:56:08 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:54469 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932519AbeFUR4H (ORCPT ); Thu, 21 Jun 2018 13:56:07 -0400 Received: by mail-wm0-f66.google.com with SMTP id o13-v6so6476397wmf.4 for ; Thu, 21 Jun 2018 10:56:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=DuO1Ofdlbp8EJhcL9UUhMWN0HhbNewTkGhy44D3euDg=; b=OQropncGzOsr2y6dgSFtZWaC913Q6ggvgF8Ez4kCwUaVAmFq1MBFTdLaGDjHH7xzAd mALWV9qRPmgvMRG/rHb775KGig6Jd7LLyTp9x+WMIVjUVSVUaOw/szywHny2WFfOsBYD aQWGxlWlhA2r28Sizfa9ptm4KvfvuJbsMTFhkVcQCGSXESZNevR3GlUI1fqS3ADHd7dL S5QjQ60zcE0NI8kSz3T6e69wZsnwXfpZpGaKiEBSRJCq+HZlWRLJQPiAyjFWbe99rwYo aLgY4tiev5UAy8dfdCmNeDcYW4MWpsQWn4lBwbsQxQ3MlTw66SXFdcIRnSyzWupvL1cr ZVKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=DuO1Ofdlbp8EJhcL9UUhMWN0HhbNewTkGhy44D3euDg=; b=g9zyBu5QyjKdg52f5ICZnJKX/w1JYk1EfSm0x+vAmH18TR0qbOsP8+iwfOpeGfQAor eA7BwCVPnEDxoaHt5ek2NNODi0YNTxVGpGyIsDmdV+261O+L95xKfXA+tzyMtzNUGy9n QivHOh1Hv760LjIjmr4zoTCtUEZHvjqHEsD+MBLh8NSDtIksT+wohhFO4wFsxWAm+rtI q5LxkoNJaewsM2PJd8YeBqM5OxY5psk69mQTsqcsQhCR/HOqaAONcrcSclvv29kh2+wv QpmEeSvA05xgumRpdkGhjWDXqLWr+PXHD9kNdBdF0eFb+9d36kItCgD2xsN2sReFUTul BTNg== X-Gm-Message-State: APt69E1zdNc+RpBSC/fW/qoawfV3/p2DR0vip8fddcGSSPBKxy5wYSws +vtZU5LVPSOlGMOhkGp1NkVrpA== X-Received: by 2002:a1c:6d02:: with SMTP id i2-v6mr5578499wmc.62.1529603766175; Thu, 21 Jun 2018 10:56:06 -0700 (PDT) Received: from ziepe.ca (S010614cc2056d97f.ed.shawcable.net. [174.3.196.123]) by smtp.gmail.com with ESMTPSA id n14-v6sm6088163wrm.23.2018.06.21.10.56.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Jun 2018 10:56:05 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.86_2) (envelope-from ) id 1fW3oP-00018T-NO; Thu, 21 Jun 2018 11:56:01 -0600 Date: Thu, 21 Jun 2018 11:56:01 -0600 From: Jason Gunthorpe To: Stefan Berger Cc: Jarkko Sakkinen , linux-integrity@vger.kernel.org, zohar@linux.vnet.ibm.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/4] tpm: Implement tpm_chip_find() and tpm_chip_put() for other subsystems Message-ID: <20180621175601.GC19270@ziepe.ca> References: <20180620204236.1572523-1-stefanb@linux.vnet.ibm.com> <20180620204236.1572523-2-stefanb@linux.vnet.ibm.com> <20180621171518.GI11859@linux.intel.com> <95b2970f-b71b-4cfc-c188-7ae7e8cb94c5@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <95b2970f-b71b-4cfc-c188-7ae7e8cb94c5@linux.vnet.ibm.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 21, 2018 at 01:45:03PM -0400, Stefan Berger wrote: > On 06/21/2018 01:15 PM, Jarkko Sakkinen wrote: > >On Wed, Jun 20, 2018 at 04:42:33PM -0400, Stefan Berger wrote: > >>Implement tpm_chip_find() for other subsystems to find a TPM chip and > >>get a reference to that chip. Once done with using the chip, the reference > >>is released using tpm_chip_put(). > >> > >>Signed-off-by: Stefan Berger > >You should sort this out in a way that we don't end up with duplicate > >functions. > > Do you want me to create a function *like* tpm_chip_find_get() that takes an > additional parameter whether to get the ops semaphore and have that function > called by the existing tpm_chip_find_get() and the new tpm_chip_find(). The > latter would then not get the ops semphore. I didn't want to do this since > one time the function returns with a lock held and the other time not. Another option, and I haven't looked, is to revise the callers of tpm_chip_find_get to not require it to hold the ops semaphore for them. Either by giving them an API to do it, or revising the TPM entry points to do it. I didn't look, but how did the ops semaphore get grabbed in your revised patches? They do grab it, right? Jason