From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Greg Kurz <groug@kaod.org>
Subject: [PULL v2 0/5] 9p queue (previous 2022-02-10)
Date: Thu, 17 Feb 2022 17:19:44 +0100 [thread overview]
Message-ID: <cover.1645114783.git.qemu_oss@crudebyte.com> (raw)
The following changes since commit c13b8e9973635f34f3ce4356af27a311c993729c:
Merge remote-tracking branch 'remotes/alistair/tags/pull-riscv-to-apply-20220216' into staging (2022-02-16 09:57:11 +0000)
are available in the Git repository at:
https://github.com/cschoenebeck/qemu.git tags/pull-9p-20220217
for you to fetch changes up to e64e27d5cb103b7764f1a05b6eda7e7fedd517c5:
9pfs: Fix segfault in do_readdir_many caused by struct dirent overread (2022-02-17 16:57:58 +0100)
----------------------------------------------------------------
9pfs: fixes and cleanup
* Fifth patch fixes a 9pfs server crash that happened on some systems due
to incorrect (system dependant) handling of struct dirent size.
* Tests: Second patch fixes a test error that happened on some systems due
mkdir() being called twice for creating the test directory for the 9p
'local' tests.
* Tests: Third patch fixes a memory leak.
* Tests: The remaining two patches are code cleanup.
----------------------------------------------------------------
Christian Schoenebeck (2):
tests/9pfs: use g_autofree where possible
tests/9pfs: fix mkdir() being called twice
Greg Kurz (2):
tests/9pfs: Fix leak of local_test_path
tests/9pfs: Use g_autofree and g_autoptr where possible
Vitaly Chikunov (1):
9pfs: Fix segfault in do_readdir_many caused by struct dirent overread
hw/9pfs/9p-synth.c | 18 +++++++--
hw/9pfs/9p-synth.h | 5 +++
hw/9pfs/codir.c | 3 +-
include/qemu/osdep.h | 13 ++++++
tests/qtest/libqos/virtio-9p.c | 38 +++++++-----------
tests/qtest/virtio-9p-test.c | 90 +++++++++++++-----------------------------
util/osdep.c | 21 ++++++++++
7 files changed, 96 insertions(+), 92 deletions(-)
next reply other threads:[~2022-02-17 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 16:19 Christian Schoenebeck [this message]
2022-02-17 16:19 ` [PULL v2 3/5] tests/9pfs: Fix leak of local_test_path Christian Schoenebeck
2022-02-17 16:19 ` [PULL v2 2/5] tests/9pfs: fix mkdir() being called twice Christian Schoenebeck
2022-02-17 16:19 ` [PULL v2 1/5] tests/9pfs: use g_autofree where possible Christian Schoenebeck
2022-02-17 16:19 ` [PULL v2 4/5] tests/9pfs: Use g_autofree and g_autoptr " Christian Schoenebeck
2022-02-17 16:19 ` [PULL v2 5/5] 9pfs: Fix segfault in do_readdir_many caused by struct dirent overread Christian Schoenebeck
2022-02-22 13:21 ` Peter Maydell
2022-02-22 13:54 ` Christian Schoenebeck
2022-02-22 15:35 ` Greg Kurz
2022-02-19 15:21 ` [PULL v2 0/5] 9p queue (previous 2022-02-10) 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=cover.1645114783.git.qemu_oss@crudebyte.com \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.