CUSE TPM fails to initialize (reason: seccomp profile) #520
Comments
stefanberger
added a commit
that referenced
this issue
Aug 13, 2021
glib's (v2.68) g_thread_pool_new() calls the syscall sched_setattr(), which we must allow to avoid termination of the CUSE TPM. Thispact resolves issue #520. Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
stefanberger
added a commit
that referenced
this issue
Aug 13, 2021
glib's (v2.68) g_thread_pool_new() calls the syscall sched_setattr(), which we must allow to avoid termination of the CUSE TPM. This patch resolves issue #520. Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
stefanberger
added a commit
that referenced
this issue
Aug 13, 2021
glib's (v2.68) g_thread_pool_new() calls the syscall sched_setattr(), which we must allow to avoid termination of the CUSE TPM. This patch resolves issue #520. Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Initialization of the CUSE TPM fails like this:
$ sudo swtpm_ioctl --tpm-device /dev/foobar -i
Could not execute PTM_INIT: Software caused connection abort
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error should occur following
swtpm_ioctl.Desktop (please complete the following information):
Versions of relevant components
The reason is due to the seccomp profile preventing the execution of
sched_setattrsyscall invoked by glib v2.68g_thread_pool_new().The text was updated successfully, but these errors were encountered: