From: Stefano Brivio <sbrivio@redhat.com>
To: passt-user@passt.top
Subject: Re: qemu couldn't connect the unix domain socket
Date: Thu, 03 Feb 2022 21:47:05 +0100 [thread overview]
Message-ID: <20220203214705.49a30ae0@elisabeth> (raw)
In-Reply-To: <20211029135231.78c55afe@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
Hello again,
On Fri, 29 Oct 2021 13:52:31 +0200
Stefano Brivio <sbrivio(a)redhat.com> wrote:
> On Fri, 29 Oct 2021 19:02:15 +0800
> Li Feng <fengli(a)smartx.com> wrote:
> >
> > [...]
> >
> > clone(child_stack=NULL,
> > flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLDstrace: Process
> > 172939 attached
> > , child_tidptr=0x7f7b89b1da10) = 172939
> > [pid 172921] exit_group(0 <unfinished ...>
> > [pid 172939] set_robust_list(0x7f7b89b1da20, 24 <unfinished ...>
> > [pid 172921] <... exit_group resumed>) = ?
> > [pid 172921] +++ exited with 0 +++
> > <... set_robust_list resumed>) = ?
> > +++ killed by SIGSYS (core dumped) +++
> > ```
> > Which is the bad syscall?
>
> Oh, it's set_robust_list(), it's normal that exit_group() doesn't
> return. That new usage probably comes from:
> https://sourceware.org/git/?p=glibc.git;a=commit;h=9a7565403758f65c07fe3705e966381d9cfd35b6
>
> and that code path is not really needed for passt, so I would have a
> quick try at avoiding it rather than adding a syscall, perhaps with a
> small replacement of daemon() using clone() instead of fork().
I forgot to follow up here: in the end I pushed a change that, among
other calls, allows set_robust_list() unconditionally:
https://passt.top/passt/commit/?id=33b1bdd079f1b40dffb040e40579d7434c28d10a
alternatives looked quite awkward, a replacement of daemon() also
didn't look very small, other suggestions warmly welcome.
By the way, the new tests checking build and basic functionality also
cover Fedora 35.
--
Stefano
prev parent reply other threads:[~2022-02-03 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 5:28 qemu couldn't connect the unix domain socket Li Feng
2021-10-28 4:25 ` Li Feng
2021-10-28 7:30 ` Stefano Brivio
2021-10-29 3:33 ` Li Feng
2021-10-29 5:27 ` Li Feng
2021-10-29 7:44 ` Stefano Brivio
2021-10-29 8:54 ` Li Feng
2021-10-29 9:34 ` Stefano Brivio
2021-10-29 11:02 ` Li Feng
2021-10-29 11:52 ` Stefano Brivio
2021-10-29 12:20 ` Li Feng
2022-02-03 20:47 ` Stefano Brivio [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=20220203214705.49a30ae0@elisabeth \
--to=sbrivio@redhat.com \
--cc=passt-user@passt.top \
/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 IMAP folder(s).