From: Stefan Berger <stefanb@linux.ibm.com>
To: linux-integrity@vger.kernel.org, jarkko@kernel.org
Cc: linux-kernel@vger.kernel.org, syzkaller@googlegroups.com,
jgg@ziepe.ca, Stefan Berger <stefanb@linux.ibm.com>,
fengaojigui88@gmail.com
Subject: [PATCH] tpm: tpm_vtpm_proxy: Try to disable queued work before flushing it
Date: Thu, 12 Nov 2026 19:11:35 -0500 [thread overview]
Message-ID: <20261113001135.1355215-1-stefanb@linux.ibm.com> (raw)
If an application opens multiple server-side TPM file descriptors using the
ioctl() on /dev/vtpmx and does not close them in the order they were
opened, then the closing of a file descriptor will run into flush_work()
and be blocked there behind other pending and active work. As a
consequence, the currently active work, that is waiting for a response to
its TPM request, will have to wait for the command to time out since its
STATE_OPENED_FLAG will not be reset. To resolve this issue, try to disable
pending work first before flushing it. The disable_work() returns quickly
and unqueues work for most of the closing file descriptors. If it returns
false, then run flush_work(), which makes sure that ongoing work ends,
which also happens quickly since its STATE_OPENED_FLAG was cleared.
Fixes: 6f99612e2500 ("tpm: Proxy driver for supporting multiple emulated TPMs")
Reported-by: fengaojigui88@gmail.com
Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
---
drivers/char/tpm/tpm_vtpm_proxy.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/char/tpm/tpm_vtpm_proxy.c b/drivers/char/tpm/tpm_vtpm_proxy.c
index b81fd2a537df..7ca5ddb0d135 100644
--- a/drivers/char/tpm/tpm_vtpm_proxy.c
+++ b/drivers/char/tpm/tpm_vtpm_proxy.c
@@ -467,7 +467,8 @@ static void vtpm_proxy_work(struct work_struct *work)
static void vtpm_proxy_work_stop(struct proxy_dev *proxy_dev)
{
vtpm_proxy_fops_undo_open(proxy_dev);
- flush_work(&proxy_dev->work);
+ if (!disable_work(&proxy_dev->work))
+ flush_work(&proxy_dev->work);
}
/*
--
2.56.0
reply other threads:[~2026-11-13 0:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261113001135.1355215-1-stefanb@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=fengaojigui88@gmail.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox