Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753833AbcCGVid (ORCPT ); Mon, 7 Mar 2016 16:38:33 -0500 Received: from lxorguk.ukuu.org.uk ([81.2.110.251]:51536 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753529AbcCGVi1 (ORCPT ); Mon, 7 Mar 2016 16:38:27 -0500 Date: Mon, 7 Mar 2016 21:38:08 +0000 From: One Thousand Gnomes To: Andy Lutomirski Cc: Stas Sergeev , Linus Torvalds , X86 ML , Linux kernel Subject: Re: sigaltstack breaks swapcontext() Message-ID: <20160307213808.35e99477@lxorguk.ukuu.org.uk> In-Reply-To: References: <568D36A1.1030706@list.ru> <568FBE50.7040504@list.ru> <569065A6.7040005@list.ru> <56DDDE51.8030006@list.ru> <56DDF0B7.1070600@list.ru> Organization: Intel Corporation X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 618 Lines: 14 > Anyway, maybe Linus or the x86 maintainers have some idea of how AC is > used. If there are people who use it for a whole program and if libc > can survive the experience, then they might expect even signal > handlers to run with AC set. But if they're sane and protect just > critical pieces of code being tested with AC, we could be polite and > clear AC on signal handler entry. No idea about AC and signals but the main use I have seen is type checking, particularly in old 16bit code. Basically code does add type to address, deference. If the type is wrong for the address you get an alignment trap. Alan