From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>,
Paul Durrant <paul@xen.org>
Subject: [PATCH 0/2] 9pfs: regression init_in_iov_from_pdu truncating size
Date: Sun, 10 May 2020 19:41:52 +0200 [thread overview]
Message-ID: <cover.1589132512.git.qemu_oss@crudebyte.com> (raw)
Stefano, looks like your original patch needs some more fine tuning:
https://bugs.launchpad.net/bugs/1877688
Please check if the assumptions I made about Xen are correct, and please
also test whether these changes still work for you with Xen as intended by
you.
Christian Schoenebeck (2):
xen-9pfs: Fix log messages of reply errors
9pfs: fix init_in_iov_from_pdu truncating size
hw/9pfs/virtio-9p-device.c | 35 ++++++++++++++++++++++++--------
hw/9pfs/xen-9p-backend.c | 41 ++++++++++++++++++++++++++++----------
2 files changed, 58 insertions(+), 18 deletions(-)
--
2.20.1
next reply other threads:[~2020-05-10 18:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 17:41 Christian Schoenebeck [this message]
2020-05-10 17:05 ` [PATCH 1/2] xen-9pfs: Fix log messages of reply errors Christian Schoenebeck
2020-05-11 22:09 ` Stefano Stabellini
2020-05-10 17:18 ` [PATCH 2/2] 9pfs: fix init_in_iov_from_pdu truncating size Christian Schoenebeck
2020-05-10 18:43 ` Christian Schoenebeck
2020-05-11 22:09 ` Stefano Stabellini
2020-05-12 11:29 ` Christian Schoenebeck
2020-05-12 23:24 ` Stefano Stabellini
2020-05-13 13:11 ` Christian Schoenebeck
2020-05-13 23:31 ` Stefano Stabellini
2020-05-14 14:24 ` Christian Schoenebeck
2020-05-14 15:51 ` Stefano Stabellini
2020-05-14 16:10 ` Christian Schoenebeck
2020-05-14 16:23 ` Stefano Stabellini
2020-05-14 16:24 ` Stefano Stabellini
2020-05-14 17:21 ` Christian Schoenebeck
2020-05-12 9:38 ` [PATCH 0/2] 9pfs: regression " Greg Kurz
2020-05-13 23:07 ` Greg Kurz
2020-05-13 23:33 ` Stefano Stabellini
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.1589132512.git.qemu_oss@crudebyte.com \
--to=qemu_oss@crudebyte.com \
--cc=anthony.perard@citrix.com \
--cc=groug@kaod.org \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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).