From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/11006 Path: news.gmane.org!.POSTED!not-for-mail From: Eric Hassold Newsgroups: gmane.linux.lib.musl.general Subject: Re: Fix pthread_create on some devices failing to initialize guard area Date: Wed, 1 Feb 2017 10:52:41 -0800 Message-ID: References: <20170120195649.GS1533@brightrain.aerifal.cx> <30588c41-eb3d-627e-c5eb-91e19ef56790@gmail.com> <20170120212933.GT1533@brightrain.aerifal.cx> <80ab9b97-dc0d-e642-cbf1-1b20e1cddf64@gmail.com> <20170131035835.GP1533@brightrain.aerifal.cx> <037fdb37-b8d3-e79d-4baf-e2581c8900bf@gmail.com> <9a395da9-2b2a-8719-f12d-c140deb12e62@gmail.com> <20170201095212.GC12395@port70.net> <72295197-bf76-b661-dcd6-6d34493a0ac0@gmail.com> <20170201183540.GT1533@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1485975176 18275 195.159.176.226 (1 Feb 2017 18:52:56 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 1 Feb 2017 18:52:56 +0000 (UTC) User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 To: musl@lists.openwall.com Original-X-From: musl-return-11021-gllmg-musl=m.gmane.org@lists.openwall.com Wed Feb 01 19:52:52 2017 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1cZ01U-0004WT-5i for gllmg-musl@m.gmane.org; Wed, 01 Feb 2017 19:52:52 +0100 Original-Received: (qmail 11383 invoked by uid 550); 1 Feb 2017 18:52:55 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 11354 invoked from network); 1 Feb 2017 18:52:54 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=h2Pv0bbWcZ3Zmv1+G2lm9vvVpp1JMWLkuAAUdbf1SF4=; b=lvQggiah/oY4cB8D9dwdo2k+g+F3Qh0llVvKVVhrCBuiwWut9d965eKSjTFAZVgo5Y qIl/cAoCC5cL33VuyooyhxvGu/yx2mAH1XmTFq4lon0ZsB41rA1LJQWr9xlGpdm7Nk4F DEWVkOekF5ownSm95r1BomxUkVo3vT/TvuqKcYcVsjQ/qfyOE163RBKpDkPnZHrXBJvs eehQp4KBkSPp/hL7hqfnVsDZT7WgJ6uBkLzttw8rtLIMMBtozULS9T3mcAM8x+2zEz7w jtdGL5L77fCnw9uuKy09uK0ujvOVxshb2DMsVjO2XPNE46APBxzypQH3MfZFpd/ChobS 2WbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=h2Pv0bbWcZ3Zmv1+G2lm9vvVpp1JMWLkuAAUdbf1SF4=; b=A8BJzQal/8kfd8m8gr7c6IbYDtcwFsNFS5kpZmGOypa/bXJiFichFlpPEId0mYrtVU o0h3UpBG1vGx+ZAzokw6Dg6EuMRjE/h6GVt8yUsBdkSZZhulaLzpbDKuK2xzZpJT0YV0 SdEf9u/Fk7T7MNigAA4xa6a0RlHXpYjaGJegLjyWITnvpa+WV6vXSYbtnzvX9NNcnPVS R6kvRywMFfJK//Op/uidzfu76aO+nYhJOZ9TgFtRka9cQogvXe4gf8odHHWqzTU16Q4K GvILqYLyLCcmWpZTJ17kr5j01AvE7lQCLfVQGQTwIw61wEPqocXHAMUlsBUweuqyTLgp 2Hzg== X-Gm-Message-State: AIkVDXKfI1w8MX+2fl7jfqzdPHDHLKvCyBgvnNv3GyyYAARR7pv1Z4mIj17/v99bIMs2ow== X-Received: by 10.84.228.194 with SMTP id y2mr6639409pli.156.1485975162888; Wed, 01 Feb 2017 10:52:42 -0800 (PST) In-Reply-To: <20170201183540.GT1533@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:11006 Archived-At: On 2/1/17 10:35 AM, Rich Felker wrote: > OK, so this was a generalization of the ABI that we weren't aware > about. Bleh. But if the rest of the world is no longer considering 4k > page size part of the ABI, we should update musl to reflect this. > >> Any further action on my side to proceed? I guess no much value in >> submitting a patch though mail here for such one liner change... > No further action needed. Thanks for being patient with my hesitance > to accept the initial patch and for working through this to find the > real problem. > > Rich Your "hesitance" reflects your consistent rigor in asking the right questions, which allows Musl to be the highly robust and clean codebase we all enjoy, and created incentive to nail the actual root cause of the issue down. So your hesitance is much appreciated.