mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: 铮 <fengaojigui88@gmail.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
	peterhuewe@gmx.de, Jason Gunthorpe <jgg@ziepe.ca>,
	linux-integrity@vger.kernel.org, syzkaller@googlegroups.com,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] tpm: prolonged stall in vtpm_proxy_fops_release() on Linux 7.3
Date: Mon, 9 Nov 2026 13:15:20 -0500	[thread overview]
Message-ID: <931108a5-e880-4b74-b5e1-8625307af8a9@linux.ibm.com> (raw)
In-Reply-To: <CAO-4RZ0Od63iUeFkoPznV4vd84Ghjii4CGo+khybQckCv=EXkQ@mail.gmail.com>



On 11/8/26 12:15 PM, 铮 wrote:
> Hi Stefan,
> 
> Thank you for the patch
> ("tpm: tpm_vtpm_proxy: Set STATE_OPENED_FLAG before inode is created").
> We applied and tested it, and we have also reproduced the boot warning
> Stefan reported and identified a sufficient condition for
> it (running without KVM acceleration). Two findings first; "Where to
> look" at the end points to the exact files in our repository.
> 
> 1. Your patch does not change the outcome of the hang
> 
[...]

> 
> v7.4-rc1 is affected as well: drivers/char/tpm/tpm_vtpm_proxy.c is
> unchanged between v7.3.0 and v7.4-rc1 (empty diff), and the same
> reproduction hangs there 1/1 (t=402s, same signature).

I have a hard time reading these .prog files. Are you closing the server 
side file descriptor you are getting back via the ioctl to /dev/tpm? 
Have a look below. If not, that could be the reason why its hanging. If 
you close it, it should clear the STATE_OPENED_FLAG and wake up any 
client waiting for a response.

/**
  * struct vtpm_proxy_new_dev - parameter structure for the
  *                             %VTPM_PROXY_IOC_NEW_DEV ioctl
  * @flags:	flags for the proxy TPM
  * @tpm_num:	index of the TPM device
  * @fd:		the file descriptor used by the proxy TPM
  * @major:	the major number of the TPM device
  * @minor:	the minor number of the TPM device
  */
struct vtpm_proxy_new_dev {
	__u32 flags;         /* input */
	__u32 tpm_num;       /* output */
	__u32 fd;            /* output */    <--- this one here
	__u32 major;         /* output */
	__u32 minor;         /* output */
};


   Stefan


      reply	other threads:[~2026-11-09 18:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-01  1:22 铮
2026-11-01 17:36 ` Jarkko Sakkinen
2026-11-02 14:02   ` Stefan Berger
2026-11-02 17:37     ` 铮
2026-11-06 19:11   ` Stefan Berger
2026-11-08 17:15     ` 铮
2026-11-09 18:15       ` Stefan Berger [this message]

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=931108a5-e880-4b74-b5e1-8625307af8a9@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=peterhuewe@gmx.de \
    --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

all inboxes | Powered by JetHome®