linux-kernel - Re: [RFC PATCH 1/1] tpm_tis: convert to using locality callbacks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1536920674.6131725.1490568027655.JavaMail.zimbra@redhat.com>
Date:   Sun, 26 Mar 2017 18:40:27 -0400 (EDT)
From:   Jerry Snitselaar <jsnitsel@...hat.com>
To:     Jason Gunthorpe <jgunthorpe@...idianresearch.com>
Cc:     tpmdd-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
        Peter Huewe <peterhuewe@....de>,
        Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        Marcel Selhorst <tpmdd@...horst.net>
Subject: Re: [RFC PATCH 1/1] tpm_tis: convert to using locality callbacks



----- Original Message -----
> From: "Jason Gunthorpe" <jgunthorpe@...idianresearch.com>
> To: "Jerry Snitselaar" <jsnitsel@...hat.com>
> Cc: tpmdd-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org, "Peter Huewe" <peterhuewe@....de>, "Jarkko
> Sakkinen" <jarkko.sakkinen@...ux.intel.com>, "Marcel Selhorst" <tpmdd@...horst.net>
> Sent: Sunday, March 26, 2017 1:36:28 PM
> Subject: Re: [RFC PATCH 1/1] tpm_tis: convert to using locality callbacks
> 
> On Sat, Mar 25, 2017 at 01:05:21PM -0700, Jerry Snitselaar wrote:
> 
> > @@ -672,7 +658,7 @@ void tpm_tis_remove(struct tpm_chip *chip)
> >  		interrupt = 0;
> >  
> >  	tpm_tis_write32(priv, reg, ~TPM_GLOBAL_INT_ENABLE & interrupt);
> > -	release_locality(chip, priv->locality, 1);
> > +	release_locality(chip, priv->locality);
> 
> Why is this done during remove? The tpm core should now keep things so
> that there is not a requested locality except during command so execution
> we should not get here with a requested locality..
> 
> Jason
> 

You're right, this call should be dropped. With release_locality always releasing
now it shouldn't have a locality when going into remove. I'll drop this in v2.

Thanks,
Jerry