From: Paolo Bonzini <pbonzini@redhat.com>
To: Claudio Fontana <cfontana@suse.de>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
qemu-devel@nongnu.org, Dario Faggioli <dfaggioli@suse.com>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH] pci: fix overflow in printf string formatting
Date: Tue, 31 May 2022 12:26:07 +0200 [thread overview]
Message-ID: <91374d96-bc7e-4bc9-de50-fe1d228ec96c@redhat.com> (raw)
In-Reply-To: <20220531092540.10151-1-cfontana@suse.de>
On 5/31/22 11:25, Claudio Fontana wrote:
> Signed-off-by: Claudio Fontana <cfontana@suse.de>
> ---
> hw/pci/pci.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/hw/pci/pci.c b/hw/pci/pci.c
> index a9b37f8000..6e7015329c 100644
> --- a/hw/pci/pci.c
> +++ b/hw/pci/pci.c
> @@ -2640,15 +2640,15 @@ static char *pci_dev_fw_name(DeviceState *dev, char *buf, int len)
> static char *pcibus_get_fw_dev_path(DeviceState *dev)
> {
> PCIDevice *d = (PCIDevice *)dev;
> - char path[50], name[33];
> - int off;
> -
> - off = snprintf(path, sizeof(path), "%s@%x",
> - pci_dev_fw_name(dev, name, sizeof name),
> - PCI_SLOT(d->devfn));
> - if (PCI_FUNC(d->devfn))
> - snprintf(path + off, sizeof(path) + off, ",%x", PCI_FUNC(d->devfn));
> - return g_strdup(path);
> + char name[33];
> + int has_func = !!PCI_FUNC(d->devfn);
> +
> + return g_strdup_printf("%s@%x%s%.*x",
> + pci_dev_fw_name(dev, name, sizeof(name)),
> + PCI_SLOT(d->devfn),
> + has_func ? "," : "",
> + has_func,
> + PCI_FUNC(d->devfn));
> }
>
> static char *pcibus_get_dev_path(DeviceState *dev)
Cc: qemu-stable@nongnu.org
prev parent reply other threads:[~2022-05-31 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 9:25 [PATCH] pci: fix overflow in printf string formatting Claudio Fontana
2022-05-31 9:25 ` Claudio Fontana
2022-05-31 9:47 ` Peter Maydell
2022-05-31 9:55 ` Claudio Fontana
2022-05-31 10:12 ` Claudio Fontana
2022-05-31 10:26 ` Paolo Bonzini [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=91374d96-bc7e-4bc9-de50-fe1d228ec96c@redhat.com \
--to=pbonzini@redhat.com \
--cc=cfontana@suse.de \
--cc=dfaggioli@suse.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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).