All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Stéphane Graber" <stgraber@ubuntu.com>
Subject: Re: [PATCH] 9p/proxy: Fix export_flags
Date: Fri, 06 Mar 2020 16:23:41 +0100	[thread overview]
Message-ID: <5999542.GsCrKgYN1H@silver> (raw)
In-Reply-To: <158349633705.1237488.8895481990204796135.stgit@bahia.lan>

On Freitag, 6. März 2020 13:05:37 CET Greg Kurz wrote:
> The common fsdev options are set by qemu_fsdev_add() before it calls
> the backend specific option parsing code. In the case of "proxy" this
> means "writeout" or "readonly" were simply ignored. This has been
> broken from the beginning.
> 
> Signed-off-by: Greg Kurz <groug@kaod.org>

Reviewed-by: Christian Schoenebeck <qemu_oss@crudebyte.com>

> ---
>  hw/9pfs/9p-proxy.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/9pfs/9p-proxy.c b/hw/9pfs/9p-proxy.c
> index 8136e1342d78..6f598a0f111c 100644
> --- a/hw/9pfs/9p-proxy.c
> +++ b/hw/9pfs/9p-proxy.c
> @@ -1139,10 +1139,10 @@ static int proxy_parse_opts(QemuOpts *opts,
> FsDriverEntry *fs, Error **errp) }
>      if (socket) {
>          fs->path = g_strdup(socket);
> -        fs->export_flags = V9FS_PROXY_SOCK_NAME;
> +        fs->export_flags |= V9FS_PROXY_SOCK_NAME;
>      } else {
>          fs->path = g_strdup(sock_fd);
> -        fs->export_flags = V9FS_PROXY_SOCK_FD;
> +        fs->export_flags |= V9FS_PROXY_SOCK_FD;
>      }
>      return 0;
>  }





      parent reply	other threads:[~2020-03-06 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06 12:05 [PATCH] 9p/proxy: Fix export_flags Greg Kurz
2020-03-06 13:04 ` no-reply
2020-03-06 13:21 ` Philippe Mathieu-Daudé
2020-03-06 15:23 ` Christian Schoenebeck [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=5999542.GsCrKgYN1H@silver \
    --to=qemu_oss@crudebyte.com \
    --cc=groug@kaod.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stgraber@ubuntu.com \
    /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.