From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org, rjones@redhat.com
Subject: Re: [PATCH] sockets: Use SOMAXCONN for Unix socket listen()
Date: Fri, 5 Feb 2021 13:04:08 -0600 [thread overview]
Message-ID: <a07ba31b-66f4-aa85-8e3b-18caec6548c6@redhat.com> (raw)
In-Reply-To: <20210205095548.GC908621@redhat.com>
On 2/5/21 3:55 AM, Daniel P. Berrangé wrote:
>> +++ b/util/qemu-sockets.c
>> @@ -1059,7 +1059,7 @@ int unix_listen(const char *str, Error **errp)
>>
>> saddr = g_new0(UnixSocketAddress, 1);
>> saddr->path = g_strdup(str);
>> - sock = unix_listen_saddr(saddr, 1, errp);
>> + sock = unix_listen_saddr(saddr, SOMAXCONN, errp);
>> qapi_free_UnixSocketAddress(saddr);
>> return sock;
>> }
>
> This method is a legacy back compat function, only used by the QEMU
> guest agent, so this can't explain the NBD problems, which use the
> QIONetListener class.
>
> IOW, the problem is in the qemu-nbd.c / blockdev-nbd.c code I believe
D'oh. Serves me right for trying to guess the spot using just a grep on
listen() rather than running under gdb with a breakpoint to find the
actual backtrace. v2 posted with a slightly changed subject line, and
this time tested to actually work.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-02-05 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 22:20 [PATCH] sockets: Use SOMAXCONN for Unix socket listen() Eric Blake
2021-02-05 9:55 ` Daniel P. Berrangé
2021-02-05 19:04 ` Eric Blake [this message]
2021-02-05 10:01 ` Richard W.M. Jones
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=a07ba31b-66f4-aa85-8e3b-18caec6548c6@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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 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).