From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
qemu-devel@nongnu.org, Paul Durrant <paul@xen.org>
Subject: Re: [PATCH 0/1] virtio-9pfs: don't truncate response
Date: Fri, 15 May 2020 11:30:02 +0200 [thread overview]
Message-ID: <20200515113002.785303e7@bahia.lan> (raw)
In-Reply-To: <cover.1589481482.git.qemu_oss@crudebyte.com>
On Thu, 14 May 2020 20:38:02 +0200
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
> The following patch reverts
> SHA-1 16724a173049ac29c7b5ade741da93a0f46edff for the virtio backend.
>
> Greg, it is intended as a quick fix for
> https://bugs.launchpad.net/bugs/1877688 at least for virtio, for the
> case the appropriate fix on Xen side might still take a while. Because
> this bug is too serious to let it rest for too long.
>
> In case Stefano comes up with a fix for Xen soon, you might just ignore
> this patch and just revert SHA-1 16724a173049ac29c7b5ade741da93a0f46edff
> entirely instead of course.
>
Stefano said he could come up with a fix in a few days, so I'll just
wait for now. If nothing happens in, say, two weeks, please ping me
and I'll merge this patch.
> Christian Schoenebeck (1):
> virtio-9pfs: don't truncate response
>
> hw/9pfs/virtio-9p-device.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
prev parent reply other threads:[~2020-05-15 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 18:38 [PATCH 0/1] virtio-9pfs: don't truncate response Christian Schoenebeck
2020-05-14 18:26 ` [PATCH 1/1] " Christian Schoenebeck
2020-05-14 19:19 ` Stefano Stabellini
2020-05-14 19:21 ` [PATCH 0/1] " Stefano Stabellini
2020-05-15 9:30 ` Greg Kurz [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=20200515113002.785303e7@bahia.lan \
--to=groug@kaod.org \
--cc=anthony.perard@citrix.com \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--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 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.