From: Andreas Schwab <schwab@suse.de>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Richard Henderson <rth@redhat.com>
Subject: Re: Incorrect IFUNC use in libpthread for fork, vfork wrapper [BZ #19861]
Date: Wed, 30 Mar 2016 13:38:00 -0000 [thread overview]
Message-ID: <mvmshz86q8e.fsf@hawking.suse.de> (raw)
In-Reply-To: <56FBD238.1010101@redhat.com> (Florian Weimer's message of "Wed, 30 Mar 2016 15:18:48 +0200")
The usual problem with a non-tail-call vfork is that subsequent calls in
the child overwrite the return address on the stack so that when vfork
returns the second time it doesn't return to the original caller in the
parent. That doesn't necessarily lead to a crash, but you get a wrong
control flow.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2016-03-30 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 13:19 Florian Weimer
2016-03-30 13:38 ` Andreas Schwab [this message]
2016-03-30 16:47 ` Richard Henderson
2016-03-30 19:10 ` Szabolcs Nagy
2016-03-30 19:51 ` Richard Henderson
2016-04-11 9:34 ` Florian Weimer
2016-04-11 9:58 ` Andreas Schwab
2016-04-11 10:02 ` Florian Weimer
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=mvmshz86q8e.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=rth@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 read-only IMAP folder(s) and NNTP newsgroup(s).