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 6D92D211B4 for ; Mon, 14 Jan 2019 16:18:22 +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:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type; q=dns; s=default; b=n1wPB xTrOIqXbMeMkY/EG/YEVQaHCEngHLC08ICsXCLAI+/Cu587DMFu9/849KtAudoVJ EaiBwp/bSa4Ly57B2vfCh1lyQSTxmx0YpHzQ322AT4GnS3eCaIQqaQ3Ep6FRBj5Q NbB/RgZg5XSPmZ6GSM93mqurd0ZCgh6aDGYiCU= 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:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type; s=default; bh=hFf3j1jSiQd NJ/b59a3rcgBJWGw=; b=CfiSSsZy5HWfYxmdC73VGpFoXJYJDaAtlpOswRgPjI6 DvzqEBpGyiSifnf2zUgpJt1uPuDeBFJbaRplNc0S5W524XHLszat6B7N1691rqCX MrVLdcmXjgK6l7pg05+l+ZgtDC+E8ePSl+FxPUlB4DrVQ+1bv9HRBnex0kRiXTi4 = Received: (qmail 112415 invoked by alias); 14 Jan 2019 16:18:20 -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 112389 invoked by uid 89); 14 Jan 2019 16:18:20 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mx1.redhat.com From: Florian Weimer To: Szabolcs Nagy Cc: Zack Weinberg , Christian Brauner , nd , GNU C Library Subject: Re: Fwd: What can a signal handler do with SIGSTKSZ? References: <874lafezhe.fsf@oldenburg2.str.redhat.com> <87sgxzdjl4.fsf@oldenburg2.str.redhat.com> <61925098-4669-b478-9baf-644818d26a44@arm.com> Date: Mon, 14 Jan 2019 17:18:15 +0100 In-Reply-To: <61925098-4669-b478-9baf-644818d26a44@arm.com> (Szabolcs Nagy's message of "Mon, 14 Jan 2019 11:18:41 +0000") Message-ID: <87d0ozb4c8.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain * Szabolcs Nagy: > i think proposing sysconf(_SC_{MIN}SIGSTKSZ) for posix is the > right solution with the kernel providing an upper bound of the > stack frame in AT_MINSIGSTKSZ (as it already does on aarch64). It's still a bit nasty for process migration, but at least it should for VM migration. I think that would be a reasonable compromise. Of course, we'd still need a way to determine how much we should add on top of AT_MINSIGSTKSZ for the application developer's benefit. 8-) Thanks, Florian