qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Rasmus Villemoes <rv@rasmusvillemoes.dk>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.com>,
	James Clarke <jrtc27@jrtc27.com>,
	Michael Karcher <debian@mkarcher.dialup.fu-berlin.de>,
	Laurent Vivier <laurent@vivier.eu>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] glibc "linux: spawni.c: simplify error reporting to parent" breaks qemu-user/Windows Service For Linux
Date: Mon, 27 Nov 2017 09:57:10 -0200	[thread overview]
Message-ID: <af9abebc-0650-a7c7-e63d-adafaa7031d6@linaro.org> (raw)
In-Reply-To: <b3becdc0-6540-30a6-b70b-8312ac5dddd9@physik.fu-berlin.de>

On 26/11/2017 18:35, John Paul Adrian Glaubitz wrote:
> On 11/26/2017 09:28 PM, John Paul Adrian Glaubitz wrote:
>> I'm not sure yet what the actual problem is but I thought it should be necessary
>> to point you at the problem.
> 
> Ok, there is already a QEMU bug report for this [1].
> 
> Adrian
> 
>> [1] https://bugs.launchpad.net/qemu/+bug/1673976
> 

We found out this potential bogus assert on 2.27 development [1] which
resulted in two fixes [2][3].

It should not be an issue for generic posix_spawn usage where there is
no expectation system/user/program kills random pids (since posix_spawn
auxiliary process has not yet returned). Some say the possible kind of
behaviour is rather undefined, but it shouldn't also trigger an assert.

I am not really sure what is happening in qemu usermode because comment
#4 in the bug reports states clone is returning an error and it should
not trigger the assert in first place.  What seems to be happening in
this scenario is clone is actually returning a success, but the auxiliary
process is being killed before actually calling execve.

In any case I think both fixes I pointed out (which are also on 2.26 and
2.25) should avoid the assert issue. Regarding the CLONE_VFORK support
I think we will need to address it on qemu.

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=22273
[2] https://sourceware.org/git/?p=glibc.git;a=commit;h=fe05e1cb6d64dba6172249c79526f1e9af8f2bfd
[3] https://sourceware.org/git/?p=glibc.git;a=commit;h=aa95a2414e4f664ca740ad5f4a72d9145abbd426

  reply	other threads:[~2017-11-27 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26 20:28 [Qemu-devel] glibc "linux: spawni.c: simplify error reporting to parent" breaks qemu-user/Windows Service For Linux John Paul Adrian Glaubitz
2017-11-26 20:35 ` John Paul Adrian Glaubitz
2017-11-27 11:57   ` Adhemerval Zanella [this message]
2017-11-27 15:24     ` Peter Maydell
2017-11-27 16:07       ` Adhemerval Zanella
2017-11-27 16:10         ` John Paul Adrian Glaubitz
2017-11-27 16:25           ` Adhemerval Zanella

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=af9abebc-0650-a7c7-e63d-adafaa7031d6@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=adhemerval.zanella@linaro.com \
    --cc=debian@mkarcher.dialup.fu-berlin.de \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=jrtc27@jrtc27.com \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=rv@rasmusvillemoes.dk \
    /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).