From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Delevoryas <peter@pjd.dev>
Cc: John Snow <jsnow@redhat.com>, Cleber Rosa <crosa@redhat.com>,
Beraldo Leal <bleal@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH RESEND] python/machine: Fix AF_UNIX path too long on macOS
Date: Wed, 6 Jul 2022 09:02:14 +0100 [thread overview]
Message-ID: <YsVBhmvAm2ANDUEt@redhat.com> (raw)
In-Reply-To: <20220705214659.73369-1-peter@pjd.dev>
On Tue, Jul 05, 2022 at 02:46:59PM -0700, Peter Delevoryas wrote:
> I noticed that I can't run any avocado tests on macOS because the QMP
> unix socket path is too long:
> I think the path limit for unix sockets on macOS might be 104 [1]
All platforms have a very limited path limit, so it isn't really
a macOS specific problem, rather....
>
> /*
> * [XSI] Definitions for UNIX IPC domain.
> */
> struct sockaddr_un {
> unsigned char sun_len; /* sockaddr len including null */
> sa_family_t sun_family; /* [XSI] AF_UNIX */
> char sun_path[104]; /* [XSI] path name (gag) */
> };
>
> The path we're using is exactly 105 characters:
>
> $ python
> Python 2.7.10 (default, Jan 19 2016, 22:24:01)
> [GCC 4.2.1 Compatible Apple LLVM 7.0.2 (clang-700.1.81)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> >>> len('/var/folders/d7/rz20f6hd709c1ty8f6_6y_z40000gn/T/avo_qemu_sock_uh3w_dgc/qemu-37331-10bacf110-monitor.sock')
It is a problem related to where the test suite is creating the
paths.
/var/folders/d7/rz20f6hd709c1ty8f6_6y_z40000gn/T/avo_qemu_sock_uh3w_dgc/
is way too deep a directory location.
It seems we just create this location using 'tempfile.TemporyDirectory'
to get a standard tmp dir.
Do you know why python is choosing
/var/folders/d7/rz20f6hd709c1ty8f6_6y_z40000gn/T/
as the temp dir ? Is that a standard location on macOS or is it
from some env variable you have set ?
> diff --git a/python/qemu/machine/machine.py b/python/qemu/machine/machine.py
> index 37191f433b..93451774e3 100644
> --- a/python/qemu/machine/machine.py
> +++ b/python/qemu/machine/machine.py
> @@ -157,7 +157,7 @@ def __init__(self,
> self._wrapper = wrapper
> self._qmp_timer = qmp_timer
>
> - self._name = name or f"qemu-{os.getpid()}-{id(self):02x}"
> + self._name = name or f"{os.getpid()}{id(self):02x}"
I don't think this is the right fix really, because IMHO the problem
is the hugely long path, rather than the final socket name.
That said, there is redundancy in the path - avocado is passing in
a dierctory created using 'tempfile.TemporyDirectory' so there is no
reason why we need to add more entropy via the POD and the 'id(self)'
hex string.
IMHO avocado should pass in the 'name' parameter explicitly, using a
plain name and thus get a shorter string.
> self._temp_dir: Optional[str] = None
> self._base_temp_dir = base_temp_dir
> self._sock_dir = sock_dir
> @@ -167,7 +167,7 @@ def __init__(self,
> self._monitor_address = monitor_address
> else:
> self._monitor_address = os.path.join(
> - self.sock_dir, f"{self._name}-monitor.sock"
> + self.sock_dir, f"{self._name}.sock"
> )
>
> self._console_log_path = console_log
> --
> 2.37.0
>
>
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 :|
next prev parent reply other threads:[~2022-07-06 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 21:46 [PATCH RESEND] python/machine: Fix AF_UNIX path too long on macOS Peter Delevoryas
2022-07-06 8:02 ` Daniel P. Berrangé [this message]
2022-07-06 16:46 ` Peter Delevoryas
2022-07-07 0:52 ` Peter Delevoryas
2022-07-07 18:46 ` Peter Delevoryas
2022-07-11 20:56 ` John Snow
2022-07-12 1:46 ` Peter Delevoryas
2022-07-12 15:14 ` John Snow
2022-07-12 8:16 ` Daniel P. Berrangé
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=YsVBhmvAm2ANDUEt@redhat.com \
--to=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=peter@pjd.dev \
--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 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).