From: Stefan Berger <stefanb@linux.ibm.com>
To: marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: Re: [PATCH] tpm: fix crash when FD >= 1024
Date: Mon, 11 Sep 2023 08:56:32 -0400 [thread overview]
Message-ID: <ede09511-9f7d-9ca9-23f6-97d3a5af1c21@linux.ibm.com> (raw)
In-Reply-To: <20230911113614.1412887-1-marcandre.lureau@redhat.com>
On 9/11/23 07:36, marcandre.lureau@redhat.com wrote:
> From: Marc-Andr Lureau <marcandre.lureau@redhat.com>
>
> Replace select() with poll() to fix a crash when QEMU has a large number
> of FDs.
>
> Fixes:
> https://bugzilla.redhat.com/show_bug.cgi?id=2020133
The description there seems wrong. It's a limit of the POSIX API not the
vTPM device driver.
>
> Signed-off-by: Marc-Andr Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
> ---
> backends/tpm/tpm_util.c | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/backends/tpm/tpm_util.c b/backends/tpm/tpm_util.c
> index a6e6d3e72f..5f4c9f5b6f 100644
> --- a/backends/tpm/tpm_util.c
> +++ b/backends/tpm/tpm_util.c
> @@ -112,12 +112,9 @@ static int tpm_util_request(int fd,
> void *response,
> size_t responselen)
> {
> - fd_set readfds;
> + GPollFD fds[1] = { {.fd = fd, .events = G_IO_IN } };
> int n;
> - struct timeval tv = {
> - .tv_sec = 1,
> - .tv_usec = 0,
> - };
> + int timeout = 1000;
>
> n = write(fd, request, requestlen);
> if (n < 0) {
> @@ -127,11 +124,8 @@ static int tpm_util_request(int fd,
> return -EFAULT;
> }
>
> - FD_ZERO(&readfds);
> - FD_SET(fd, &readfds);
> -
> /* wait for a second */
> - n = select(fd + 1, &readfds, NULL, NULL, &tv);
> + n = RETRY_ON_EINTR(g_poll(fds, 1, timeout));
> if (n != 1) {
> return -errno;
> }
prev parent reply other threads:[~2023-09-11 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 11:36 [PATCH] tpm: fix crash when FD >= 1024 marcandre.lureau
2023-09-11 11:45 ` Michael Tokarev
2023-09-11 12:56 ` 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=ede09511-9f7d-9ca9-23f6-97d3a5af1c21@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).