On 11/6/25 2:41 PM, Vladimir Sementsov-Ogievskiy wrote:
The code tends to include errno into error messages after
tpm_util_test_tpmdev() and tpm_emulator_ctrlcmd() calls.

Both has error paths, where errno is not set, examples:

tpm_emulator_ctrlcmd()
   qemu_chr_fe_write_all()
     qemu_chr_write()
       replay_char_write_event_load()
         ...
         *res = replay_get_dword();
         ...

tpm_util_test_tpmdev()
   tpm_util_test()
     tpm_util_request()
       ...
       if (n != requestlen) {
           return -EFAULT;
       }
       ...

Both doesn't document that they set errno.

Let's drop these explicit usage of errno. If we need this information,
it should be added to errp deeper in the stack.

Signed-off-by: Vladimir Sementsov-Ogievskiy <[email protected]>

Reviewed-by: Stefan Berger <[email protected]>

Reply via email to