From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13532 Path: news.gmane.org!.POSTED!not-for-mail From: Florian Weimer Newsgroups: gmane.linux.lib.musl.general Subject: Re: aio_cancel segmentation fault for in progress write requests Date: Fri, 07 Dec 2018 21:06:18 +0100 Message-ID: <87h8fpaypx.fsf@oldenburg2.str.redhat.com> References: <20181207154419.GD23599@brightrain.aerifal.cx> <20181207165217.GE23599@brightrain.aerifal.cx> <54b4d253-1660-3207-5d59-f23f1c25b2b9@adelielinux.org> <20181207182650.GF23599@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1544213075 19283 195.159.176.226 (7 Dec 2018 20:04:35 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 7 Dec 2018 20:04:35 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) Cc: musl@lists.openwall.com To: Rich Felker Original-X-From: musl-return-13548-gllmg-musl=m.gmane.org@lists.openwall.com Fri Dec 07 21:04:31 2018 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 1gVMML-0004le-Pc for gllmg-musl@m.gmane.org; Fri, 07 Dec 2018 21:04:25 +0100 Original-Received: (qmail 22412 invoked by uid 550); 7 Dec 2018 20:06:34 -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 22394 invoked from network); 7 Dec 2018 20:06:34 -0000 In-Reply-To: <20181207182650.GF23599@brightrain.aerifal.cx> (Rich Felker's message of "Fri, 7 Dec 2018 13:26:50 -0500") X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.47]); Fri, 07 Dec 2018 20:06:22 +0000 (UTC) Xref: news.gmane.org gmane.linux.lib.musl.general:13532 Archived-At: * Rich Felker: > I don't think so. I'm concerned that it's a stack overflow, and that > somehow the kernel folks have managed to break the MINSIGSTKSZ ABI. Probably: It's a nasty CPU backwards compatibility problem. Some of the suggestions I made to work around this are simply wrong; don't take them too seriously. Nowadays, the kernel has a way to disable the %zmm registers, but it unfortunately does not reduce the save area size. Thanks, Florian