From: Wei Xu <wexu@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: armbru@redhat.com, amit.shah@redhat.com, berrange@redhat.com,
jasowang@redhat.com, mprivozn@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC Patch 2/3] chardev: save the passed in 'fd' parameter during parsing
Date: Thu, 2 Jun 2016 00:20:18 +0800 [thread overview]
Message-ID: <574F0B42.2010306@redhat.com> (raw)
In-Reply-To: <574DC93E.4000700@redhat.com>
On 2016年06月01日 01:26, Eric Blake wrote:
> On 05/31/2016 10:30 AM, wexu@redhat.com wrote:
>> From: Wei Xu <wexu@redhat.com>
>>
>> Save the 'fd' paramter as unix socket 'sockfd' member.
>>
>> Signed-off-by: Wei Xu <wexu@redhat.com>
>> ---
>> qemu-char.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/qemu-char.c b/qemu-char.c
>> index ea9c02e..8d20494 100644
>> --- a/qemu-char.c
>> +++ b/qemu-char.c
>> @@ -3664,6 +3664,7 @@ static void qemu_chr_parse_socket(QemuOpts *opts, ChardevBackend *backend,
>> bool is_telnet = qemu_opt_get_bool(opts, "telnet", false);
>> bool do_nodelay = !qemu_opt_get_bool(opts, "delay", true);
>> int64_t reconnect = qemu_opt_get_number(opts, "reconnect", 0);
>> + const int32_t fd = (int32_t)qemu_opt_get_number(opts, "sockfd", 0);
>> const char *path = qemu_opt_get(opts, "path");
>> const char *host = qemu_opt_get(opts, "host");
>> const char *port = qemu_opt_get(opts, "port");
>> @@ -3708,6 +3709,12 @@ static void qemu_chr_parse_socket(QemuOpts *opts, ChardevBackend *backend,
>> addr->type = SOCKET_ADDRESS_KIND_UNIX;
>> q_unix = addr->u.q_unix.data = g_new0(UnixSocketAddress, 1);
>> q_unix->path = g_strdup(path);
>> +
>> + if (fd) {
>> + q_unix->sockfd = fd;
>> + } else {
>> + q_unix->sockfd = 0;
>
> 0 is a valid fd number; this risks accidentally closing stdin later on.
> Please use -1 for unset, if you must store an fd number. But given my
> comments on patch 1, I'm not sure that you need this addition.
Thanks for your comment, i just wonder what's the motivation of
qemu_open(), seems it's more like an regular file consideration, is it?
can it be easily expended to socket file?
>
next prev parent reply other threads:[~2016-06-01 16:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1464712247-11655-1-git-send-email-wexu@redhat.com>
[not found] ` <574DC83B.9010802@redhat.com>
2016-06-01 15:44 ` [Qemu-devel] [RFC Patch 0/3] Accept passed in socket 'fd' open from outside for unix socket Wei Xu
[not found] ` <20160531164448.GE21628@redhat.com>
2016-06-01 16:16 ` Wei Xu
2016-06-02 7:41 ` Michal Privoznik
2016-06-02 8:29 ` Daniel P. Berrange
2016-06-02 11:38 ` Michal Privoznik
2016-06-02 18:07 ` Wei Xu
2016-06-03 8:32 ` Daniel P. Berrange
2016-06-08 10:07 ` Amnon Ilan
[not found] ` <20160608212738.GH3073@plex>
[not found] ` <f7tvb1jxsfq.fsf@redhat.com>
2016-06-09 7:46 ` Amnon Ilan
2016-06-09 9:16 ` Daniel P. Berrange
2016-06-13 8:57 ` Michal Privoznik
2016-06-14 8:03 ` Wei Xu
2016-06-14 8:17 ` Daniel P. Berrange
2016-06-14 14:23 ` Aaron Conole
2016-06-14 17:50 ` Wei Xu
2016-06-14 12:47 ` Amnon Ilan
2016-06-14 14:21 ` Aaron Conole
2016-06-02 19:27 ` [Qemu-devel] Channel paths (was: Re: [RFC Patch 0/3] Accept passed in socket 'fd' open from outside for unix socket) Sascha Silbe
[not found] ` <201606021927.u52JB3YU031760@mx0a-001b2d01.pphosted.com>
2016-06-03 8:34 ` Daniel P. Berrange
2016-06-07 18:44 ` [Qemu-devel] Channel paths Sascha Silbe
2016-06-22 15:24 ` [Qemu-devel] [RFC Patch 0/3] Accept passed in socket 'fd' open from outside for unix socket Wei Xu
[not found] ` <1464712247-11655-3-git-send-email-wexu@redhat.com>
[not found] ` <574DC93E.4000700@redhat.com>
2016-06-01 16:20 ` Wei Xu [this message]
2016-06-22 15:26 ` [Qemu-devel] [RFC Patch 2/3] chardev: save the passed in 'fd' parameter during parsing Wei Xu
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=574F0B42.2010306@redhat.com \
--to=wexu@redhat.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=mprivozn@redhat.com \
--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 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.