From: Greg Kurz <groug@kaod.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, Greg Kurz <groug@kaod.org>
Subject: [Qemu-devel] [PULL 07/14] 9pfs: fix error path in pdu_submit()
Date: Mon, 8 Jan 2018 15:28:24 +0100 [thread overview]
Message-ID: <20180108142831.6638-8-groug@kaod.org> (raw)
In-Reply-To: <20180108142831.6638-1-groug@kaod.org>
If we receive an unsupported request id, we first decide to
return -ENOTSUPP to the client, but since the request id
causes is_read_only_op() to return false, we change the
error to be -EROFS if the fsdev is read-only. This doesn't
make sense since we don't know what the client asked for.
This patch ensures that -EROFS can only be returned if the
request id is supported.
Signed-off-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Eric Blake <eblake@redhat.com>
---
hw/9pfs/9p.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
index 76f90f2b7863..558efb41defd 100644
--- a/hw/9pfs/9p.c
+++ b/hw/9pfs/9p.c
@@ -3473,14 +3473,12 @@ void pdu_submit(V9fsPDU *pdu, P9MsgHeader *hdr)
if (pdu->id >= ARRAY_SIZE(pdu_co_handlers) ||
(pdu_co_handlers[pdu->id] == NULL)) {
handler = v9fs_op_not_supp;
+ } else if (is_ro_export(&s->ctx) && !is_read_only_op(pdu)) {
+ handler = v9fs_fs_ro;
} else {
handler = pdu_co_handlers[pdu->id];
}
- if (is_ro_export(&s->ctx) && !is_read_only_op(pdu)) {
- handler = v9fs_fs_ro;
- }
-
qemu_co_queue_init(&pdu->complete);
co = qemu_coroutine_create(handler, pdu);
qemu_coroutine_enter(co);
--
2.13.6
next prev parent reply other threads:[~2018-01-08 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 14:28 [Qemu-devel] [PULL 00/14] 9p patches for 2.12 20180108 Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 01/14] virtio-9p: move unrealize/realize after virtio_9p_transport definition Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 02/14] 9pfs: fix XattrOperations typedef Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 03/14] fsdev: fix some type definitions Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 04/14] 9pfs: " Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 05/14] 9pfs: handle: fix type definition Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 06/14] 9pfs: fix type in *_parse_opts declarations Greg Kurz
2018-01-08 14:28 ` Greg Kurz [this message]
2018-01-08 14:28 ` [Qemu-devel] [PULL 08/14] 9pfs: make pdu_marshal() and pdu_unmarshal() static functions Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 09/14] tests: virtio-9p: fix ISR dependence Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 10/14] tests: virtio-9p: set DRIVER_OK before using the device Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 11/14] fsdev: improve error handling of backend opts parsing Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 12/14] fsdev: improve error handling of backend init Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 13/14] 9pfs: deprecate handle backend Greg Kurz
2018-01-08 14:28 ` [Qemu-devel] [PULL 14/14] MAINTAINERS: Drop Aneesh as 9pfs maintainer Greg Kurz
2018-01-09 9:47 ` [Qemu-devel] [PULL 00/14] 9p patches for 2.12 20180108 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=20180108142831.6638-8-groug@kaod.org \
--to=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 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).