All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
	"Peter Lieven" <pl@kamp.de>,
	"Richard W.M. Jones" <rjones@redhat.com>,
	qemu-devel@nongnu.org, "Kevin Wolf" <kwolf@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Konstantin Kostiuk" <kkostiuk@redhat.com>,
	qemu-block@nongnu.org
Subject: Re: [PATCH for-9.1 6/9] block/nbd: Use URI parsing code from glib
Date: Thu, 28 Mar 2024 14:59:56 +0000	[thread overview]
Message-ID: <ZgWF7MGNAlMb_WvY@redhat.com> (raw)
In-Reply-To: <sv4rp7w2cnjy5xykp4t3w5gf3zwnohe5eso422whl2ux2ofixa@xwjphousol77>

On Thu, Mar 28, 2024 at 09:54:49AM -0500, Eric Blake wrote:
> On Thu, Mar 28, 2024 at 03:06:03PM +0100, Thomas Huth wrote:
> > Since version 2.66, glib has useful URI parsing functions, too.
> > Use those instead of the QEMU-internal ones to be finally able
> > to get rid of the latter. The g_uri_get_host() also takes care
> > of removing the square brackets from IPv6 addresses, so we can
> > drop that part of the QEMU code now, too.
> > 
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> >  block/nbd.c | 66 ++++++++++++++++++++++++++++++-----------------------
> >  1 file changed, 38 insertions(+), 28 deletions(-)
> > 
> > diff --git a/block/nbd.c b/block/nbd.c
> > index ef05f7cdfd..95b507f872 100644
> > --- a/block/nbd.c
> > +++ b/block/nbd.c
> > @@ -31,7 +31,6 @@
> >  #include "qemu/osdep.h"
> >  
> >  #include "trace.h"
> > -#include "qemu/uri.h"
> >  #include "qemu/option.h"
> >  #include "qemu/cutils.h"
> >  #include "qemu/main-loop.h"
> > @@ -1514,30 +1513,34 @@ static void nbd_client_close(BlockDriverState *bs)
> >  
> >  static int nbd_parse_uri(const char *filename, QDict *options)
> >  {
> > -    URI *uri;
> > +    GUri *uri;
> 
> Is it worth using 'g_autoptr(GUri) uri = NULL;' here, to simplify cleanup later?
> 
> >      const char *p;
> > -    QueryParams *qp = NULL;
> > +    GHashTable *qp = NULL;
> 
> Presumably would be easier if qp is also auto-free.
> 
> > +    int qp_n;
> >      int ret = 0;
> >      bool is_unix;
> > +    const char *uri_scheme, *uri_query, *uri_server;
> > +    int uri_port;
> >  
> > -    uri = uri_parse(filename);
> > +    uri = g_uri_parse(filename, G_URI_FLAGS_NONE, NULL);
> 
> The glib API is fairly close to what we have in qemu, making this a
> nice switchover.
> 
> >          /* nbd[+tcp]://host[:port]/export */
> > -        if (!uri->server) {
> > +        if (!uri_server) {
> >              ret = -EINVAL;
> >              goto out;
> >          }
> >  
> > -        /* strip braces from literal IPv6 address */
> > -        if (uri->server[0] == '[') {
> > -            host = qstring_from_substr(uri->server, 1,
> > -                                       strlen(uri->server) - 1);
> > -        } else {
> > -            host = qstring_from_str(uri->server);
> > -        }
> > -
> >          qdict_put_str(options, "server.type", "inet");
> > -        qdict_put(options, "server.host", host);
> > +        qdict_put_str(options, "server.host", uri_server);
> >  
> > -        port_str = g_strdup_printf("%d", uri->port ?: NBD_DEFAULT_PORT);
> > +        port_str = g_strdup_printf("%d", uri_port != -1 ? uri_port
> > +                                                        : NBD_DEFAULT_PORT);
> >          qdict_put_str(options, "server.port", port_str);
> 
> If a user requests nbd://hostname:0/export, this now sets server.port
> to "0" instead of "10809".  Is that an intentional change?  No one
> actually passes an explicit ":0" port on purpose, but we do have to
> worry about malicious URIs.

Passing '0' will cause the kernel to allocate a random free
port, so that is potentially introducing new semantics ?


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2024-03-28 15:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 14:05 [PATCH for-9.1 0/9] Switch to glib URI parsing code Thomas Huth
2024-03-28 14:05 ` [PATCH for-9.1 1/9] tests: Remove Ubuntu 20.04 container Thomas Huth
2024-03-28 14:05 ` [PATCH for-9.1 2/9] tests/lcitool/libvirt-ci: Update to the latest master branch Thomas Huth
2024-03-28 14:06 ` [PATCH for-9.1 3/9] tests: Update our CI to use CentOS Stream 9 instead of 8 Thomas Huth
2024-03-28 14:06 ` [PATCH for-9.1 4/9] Bump minimum glib version to v2.66 Thomas Huth
2024-04-12 10:16   ` Paolo Bonzini
2024-04-12 10:58     ` Thomas Huth
2024-04-12 12:01       ` Paolo Bonzini
2024-03-28 14:06 ` [PATCH for-9.1 5/9] block/gluster: Use URI parsing code from glib Thomas Huth
2024-03-28 14:06 ` [PATCH for-9.1 6/9] block/nbd: " Thomas Huth
2024-03-28 14:13   ` Richard W.M. Jones
2024-03-28 15:06     ` Eric Blake
2024-03-28 16:40       ` Richard W.M. Jones
2024-04-04  9:47         ` Richard W.M. Jones
2024-03-28 14:54   ` Eric Blake
2024-03-28 14:59     ` Daniel P. Berrangé [this message]
2024-03-28 15:34       ` Thomas Huth
2024-03-28 14:06 ` [PATCH for-9.1 7/9] block/nfs: " Thomas Huth
2024-03-28 14:06 ` [PATCH for-9.1 8/9] block/ssh: " Thomas Huth
2024-03-28 14:15   ` Richard W.M. Jones
2024-03-28 14:06 ` [PATCH for-9.1 9/9] util/uri: Remove the old URI parsing code Thomas Huth
2024-04-15 14:16 ` MAINTAINERS tweak [was: [PATCH for-9.1 0/9] Switch to glib URI parsing code] Eric Blake

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=ZgWF7MGNAlMb_WvY@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kkostiuk@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=pl@kamp.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=thuth@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    /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.