[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] tpm: Return QMP error when TPM is disabled in build
From: |
Philippe Mathieu-Daudé |
Subject: |
Re: [PATCH] tpm: Return QMP error when TPM is disabled in build |
Date: |
Wed, 9 Jun 2021 19:34:32 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 |
On 6/9/21 7:27 PM, Philippe Mathieu-Daudé wrote:
> On 6/9/21 6:01 PM, Marc-André Lureau wrote:
>> Hi
>>
>> On Wed, Jun 9, 2021 at 7:33 PM Philippe Mathieu-Daudé <philmd@redhat.com
>> <mailto:philmd@redhat.com>> wrote:
>>
>> When the management layer queries a binary built using --disable-tpm
>> for TPM devices, it gets confused by getting empty responses:
>>
>> { "execute": "query-tpm" }
>> {
>> "return": [
>> ]
>> }
>> { "execute": "query-tpm-types" }
>> {
>> "return": [
>> ]
>> }
>> { "execute": "query-tpm-models" }
>> {
>> "return": [
>> ]
>> }
>>
>> Make it clearer by returning an error, mentioning the feature is
>> disabled:
>>
>> { "execute": "query-tpm" }
>> {
>> "error": {
>> "class": "GenericError",
>> "desc": "this feature or command is not currently supported"
>> }
>> }
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com
>> <mailto:philmd@redhat.com>>
>>
>>
>> Why not make the qapi schema conditional?
Using your suggestion (and ignoring QAPI marshaling error) I'm getting:
{ "execute": "query-tpm" }
{
"error": {
"class": "CommandNotFound",
"desc": "The command query-tpm has not been found"
}
}
Is that OK from a management perspective?