From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fabian Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server] test: fix restore config test as unprivileged user
Date: Fri, 18 Jun 2021 17:46:21 +0200 [thread overview]
Message-ID: <b5e81491-69e7-769f-8b1b-fa3747387fce@proxmox.com> (raw)
In-Reply-To: <20210531142710.31410-1-f.ebner@proxmox.com>
On 31.05.21 16:27, Fabian Ebner wrote:
> Is that the intended behavior?
it effectively comes from the IPCC code's call to qb_ipcc_connect
where something (did not checked to closely) tries to do an open of /tmp with
read-write, where the write part on the directory makes no sense.
...
setsockopt(3, SOL_SOCKET, SO_PASSCRED, [0], 4) = 0
openat(AT_FDCWD, "/dev/shm/qb-", O_RDWR) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/tmp/", O_RDWR) = -1 EISDIR (Is a directory)
Maybe some odd fallback logic on libqb or parts, not sure, maybe ask around the
#kronosnet IRC channel (IIRC they moved to libera after the freenode fallout).
prev parent reply other threads:[~2021-06-18 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 14:27 Fabian Ebner
2021-06-18 15:26 ` [pve-devel] applied: " Thomas Lamprecht
2021-06-18 15:46 ` Thomas Lamprecht [this message]
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=b5e81491-69e7-769f-8b1b-fa3747387fce@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.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