From: Markus Armbruster <armbru@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "xiaoqiang zhao" <zxq_yx_007@163.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [PULL 1/3] qemu-sockets: add abstract UNIX domain socket support
Date: Wed, 20 May 2020 16:23:50 +0200 [thread overview]
Message-ID: <87imgqr8g9.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20200520130025.2201467-2-berrange@redhat.com> ("Daniel P. =?utf-8?Q?Berrang=C3=A9=22's?= message of "Wed, 20 May 2020 14:00:23 +0100")
I apologize for chiming in so late...
Daniel P. Berrangé <berrange@redhat.com> writes:
> From: xiaoqiang zhao <zxq_yx_007@163.com>
>
> unix_listen/connect_saddr now support abstract address types
>
> two aditional BOOL switches are introduced:
> tight: whether to set @addrlen to the minimal string length,
> or the maximum sun_path length. default is TRUE
When and why would anyone pass 'tight': false?
> abstract: whether we use abstract address. default is FALSE
>
> cli example:
> -monitor unix:/tmp/unix.socket,abstract,tight=off
> OR
> -chardev socket,path=/tmp/unix.socket,id=unix1,abstract,tight=on
>
> Signed-off-by: xiaoqiang zhao <zxq_yx_007@163.com>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
next prev parent reply other threads:[~2020-05-20 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 13:00 [PULL 0/3] Socket next patches Daniel P. Berrangé
2020-05-20 13:00 ` [PULL 1/3] qemu-sockets: add abstract UNIX domain socket support Daniel P. Berrangé
2020-05-20 14:23 ` Markus Armbruster [this message]
2020-05-20 14:33 ` Daniel P. Berrangé
2020-05-20 13:00 ` [PULL 2/3] tests/util-sockets: add abstract unix socket cases Daniel P. Berrangé
2020-05-20 13:00 ` [PULL 3/3] qemu-options: updates for abstract unix sockets Daniel P. Berrangé
2020-05-21 18:58 ` [PULL 0/3] Socket next patches 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=87imgqr8g9.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zxq_yx_007@163.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.