On 11/17/2017 07:17 PM, Jason Gunthorpe wrote: > On Fri, Nov 17, 2017 at 07:10:09PM +0100, Javier Martinez Canillas wrote: > >> Right, that's what I understood indeed but wanted to be sure. The problem with >> that approach is that would not scale. >> >> Since this particular TPM2 doesn't have support for the TPM2_EncryptDecrypt2 >> command, but some chips may not support others commands. > > No, tpm_validate is not supposed to be sensitive to what commands the > TPM supports. It is only supposed to check if the command passed is > fully understood by the kernel and is properly formed. > > This is to prevent rouge user space from sending garbage or privileged > commands to the TPM. > > If it is refusing TPM2_EncryptDecrypt2, and that command is safe to > use in the spaces system, then tpm_validate must learn how to handle > it, or userspace can never use it. > I see, misunderstood what the check was about then. If that's the case, then Making tpm_validate to learn how to check that command makes sense indeed and so does the -EINVAL error code. Since it doesn't mean that the TPM doesn't support the command but just that the TPM spaces doesn't know how to handle it. Need to look at the code in more detail, thanks a lot for the clarification. > Jason > Best regards, -- Javier Martinez Canillas Software Engineer - Desktop Hardware Enablement Red Hat
