From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 104089 invoked by alias); 14 Jan 2019 16:15:25 -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 103988 invoked by uid 89); 14 Jan 2019 16:15:14 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=unavailable version=3.3.2 spammy=heard, Christian, christian, somewhere X-HELO: mx1.redhat.com From: Florian Weimer To: Christian Brauner Cc: libc-alpha@sourceware.org, Zack Weinberg Subject: Re: Fwd: What can a signal handler do with SIGSTKSZ? References: <874lafezhe.fsf@oldenburg2.str.redhat.com> <87zhs7dk90.fsf@oldenburg2.str.redhat.com> <50075560-E190-4E6E-8DB6-CAA0BE34D8F0@brauner.io> Date: Mon, 14 Jan 2019 16:15:00 -0000 In-Reply-To: <50075560-E190-4E6E-8DB6-CAA0BE34D8F0@brauner.io> (Christian Brauner's message of "Fri, 11 Jan 2019 21:26:31 +0100") Message-ID: <87h8ebb4hn.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 X-SW-Source: 2019-01/txt/msg00291.txt.bz2 * Christian Brauner: >> > Hm it looks like the bug report didn't see any response. This is the > first time I heard about it. Sorry for repeating: has this been > brought up somewhere on a kernel mailing list? I don't remember a discussion. Thanks, Florian