From: "Cédric Le Goater" <clg@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>
Subject: [PULL 0/2] vfio queue
Date: Wed, 24 May 2023 10:47:22 +0200 [thread overview]
Message-ID: <20230524084724.2511267-1-clg@redhat.com> (raw)
The following changes since commit aa33508196f4e2da04625bee36e1f7be5b9267e7:
Merge tag 'mem-2023-05-23' of https://github.com/davidhildenbrand/qemu into staging (2023-05-23 10:57:25 -0700)
are available in the Git repository at:
https://github.com/legoater/qemu/ tags/pull-vfio-20230524
for you to fetch changes up to dbdea0dbfe2cef9ef6c752e9077e4fc98724194c:
util/vfio-helpers: Use g_file_read_link() (2023-05-24 09:21:22 +0200)
----------------------------------------------------------------
vfio queue:
* Fix for a memory corruption due to an extra free
* Fix for a compile breakage
----------------------------------------------------------------
Akihiko Odaki (1):
util/vfio-helpers: Use g_file_read_link()
Zhenzhong Duan (1):
vfio/pci: Fix a use-after-free issue
hw/vfio/pci.c | 2 +-
util/vfio-helpers.c | 8 +++++---
2 files changed, 6 insertions(+), 4 deletions(-)
next reply other threads:[~2023-05-24 8:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 8:47 Cédric Le Goater [this message]
2023-05-24 8:47 ` [PULL 1/2] vfio/pci: Fix a use-after-free issue Cédric Le Goater
2023-05-24 8:47 ` [PULL 2/2] util/vfio-helpers: Use g_file_read_link() Cédric Le Goater
2023-05-25 0:46 ` [PULL 0/2] vfio queue Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2024-01-29 8:41 Cédric Le Goater
2024-01-29 17:22 ` Peter Maydell
2024-03-10 19:19 Cédric Le Goater
2024-03-12 11:05 ` Peter Maydell
2024-11-05 16:58 Cédric Le Goater
2024-11-06 17:28 ` Peter Maydell
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=20230524084724.2511267-1-clg@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).