From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 1CF95211B4 for ; Mon, 14 Jan 2019 18:19:51 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; q=dns; s=default; b=RE9fW nlf3U0VVQzwF9Tr+UV4T2DxV29/lHJDQDEWDXBfX9KqzUCA4QGwcQLwPmzCHvKtx EnbihRKClkSBSz2qxPMqpyY6Wqr/D0Hxcbhok6FlxMXHe5xdFw2US3pYElCioRhY N5qJBkejKnQ0Uzdq1c5OuAxb0eMgGtZQT4rUlg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; s=default; bh=IsH8iEUKv2I HAQe2zwxdO2nuwWs=; b=bV/RPu+Hdw09Chsekmkhmq1Vtpa/uCDYnncfAYKyGqy ySb84lz2/BEiGVSaS7Trw5aFoZAOFtCvCz6KoGDAVC1QgsIC7Em5AzXvMj1Kpzme GtDA1cMMxQv2XPRC7erebhg8gxR7FVrCIrGhJKv3O9wlKaqckAGymIaTYdcdGz4I = 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-Unsubscribe: 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-HELO: relay1.mentorg.com Date: Mon, 14 Jan 2019 18:19:40 +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" 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