From: "LeMay, Michael" <michael.lemay@intel.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: [RFC PATCH v2 2/4] support SafeStack in init and threading
Date: Wed, 2 Nov 2016 14:50:15 -0700 [thread overview]
Message-ID: <217e8254-8629-2a75-b717-43ebcc43ea6c@intel.com> (raw)
In-Reply-To: <20161102174031.GI5749@port70.net>
On 11/2/2016 10:40, Szabolcs Nagy wrote:
> * LeMay, Michael <michael.lemay@intel.com> [2016-11-02 09:56:14 -0700]:
>> On 11/1/2016 16:52, Szabolcs Nagy wrote:
>>> * LeMay, Michael <michael.lemay@intel.com> [2016-10-28 20:00:24 +0000]:
>> ...
>>>> + if (pthread_getattr_np(self, &attr) != 0)
>>>> + a_crash();
>>> this may have significant startup overhead because determining
>>> the main stack size is not optimized.
>> I could use a constant stack size here instead. However, this will be
>> needed for supporting a separate stack segment, since it is used to
>> determine the proper limit for the DS and ES segments.
> ok
>
> the pthread_* symbol should be moved to the reserved
> namespace (__pthread_*) since this code will get
> static linked into iso c conforming code which is
> allowed to redefine pthread_*.
pthread_getattr_np and pthread_attr_getstack currently have strong
definitions in musl. Are you proposing that I rename the existing
definitions into the __pthread_* namespace and add weak aliases?
By the way, I need to update my patch of __pthread_create to pass
new->stack as the second parameter to __clone, since
__safestack_init_thread updates that field.
prev parent reply other threads:[~2016-11-02 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 20:00 LeMay, Michael
2016-11-01 23:52 ` Szabolcs Nagy
2016-11-02 16:56 ` LeMay, Michael
2016-11-02 17:40 ` Szabolcs Nagy
2016-11-02 21:50 ` LeMay, Michael [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=217e8254-8629-2a75-b717-43ebcc43ea6c@intel.com \
--to=michael.lemay@intel.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).