From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29151 invoked by alias); 14 Jan 2019 18:19:49 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 29142 invoked by uid 89); 14 Jan 2019 18:19:48 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=commitment, fair X-HELO: relay1.mentorg.com Date: Mon, 14 Jan 2019 18:19:00 -0000 From: Joseph Myers To: Carlos O'Donell CC: Florian Weimer , Szabolcs Nagy , Zack Weinberg , Christian Brauner , nd , GNU C Library Subject: Re: Fwd: What can a signal handler do with SIGSTKSZ? In-Reply-To: <0a995c61-62d6-7b09-8b5d-1d77b33a242d@redhat.com> Message-ID: References: <874lafezhe.fsf@oldenburg2.str.redhat.com> <87sgxzdjl4.fsf@oldenburg2.str.redhat.com> <61925098-4669-b478-9baf-644818d26a44@arm.com> <87d0ozb4c8.fsf@oldenburg2.str.redhat.com> <0a995c61-62d6-7b09-8b5d-1d77b33a242d@redhat.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2019-01/txt/msg00299.txt.bz2 On Mon, 14 Jan 2019, Carlos O'Donell wrote: > If *I* were a developer I might expect as Zach pointed out, that I can call > every function on the list of callable AS-safe functions, at least once, > without recursion, and expect them to operate correctly. > > A test case for this would therefore be a main, that register a handler > that exercises *all* functions in the AS-safe list, and then looks for > stack corruption at each execution. The POSIX AS-safe list, or the functions that are currently documented as AS-safe in glibc (an observed property, not necessarily a commitment to an API)? (strtold uses a fair amount of stack, for example, and is listed as AS-safe in glibc.) -- Joseph S. Myers joseph@codesourcery.com