Thread (26 messages) 26 messages, 6 authors, 2017-10-26

Re: [tpmdd-devel] [PATCH] tpm: remove chip_num parameter from in-kernel API

From: Jarkko Sakkinen <hidden>
Date: 2017-10-24 14:06:21
Also in: keyrings, linux-crypto, linux-security-module, lkml

On Mon, Oct 23, 2017 at 10:07:31AM -0400, Stefan Berger wrote:
I think every kernel internal TPM driver API should be called with the
tpm_chip as a parameter. This is in foresight of namespacing of IMA where we
want to provide the flexibility of passing a dedicated vTPM to each
namespace and IMA would use the chip as a parameter to all of these
functions to talk to the right tpm_vtpm_proxy instance. From that
perspective this patch goes into the wrong direction.

   Stefan
The goal of this patch is to kernel code that never gets executed. It
removes a load of completely dead code. It is the only thing that this
commit does. Why do you think this is "going into wrong direction" if it
only removes dead code and refines the documentation up to date?

After the dead code has been removed it makes sense to propose a better
mechanism. Maybe the one that you are speaking about. But you need to
remove the cruft first.

/Jarkko
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help