From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752392AbbHRGkb (ORCPT <rfc822;w@1wt.eu>);
	Tue, 18 Aug 2015 02:40:31 -0400
Received: from smtp51.i.mail.ru ([94.100.177.111]:47878 "EHLO smtp51.i.mail.ru"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750822AbbHRGka (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 18 Aug 2015 02:40:30 -0400
Subject: Re: [regression] x86/signal/64: Fix SS handling for signals delivered
 to 64-bit programs breaks dosemu
To: Linus Torvalds <torvalds@linux-foundation.org>
References: <55CA90B4.2010205@list.ru>
 <CA+55aFw5DzEn+jYmY0KwbkytBzowo45o3Czh1cQZ_aaR1+WZYA@mail.gmail.com>
 <55CCD921.4040301@list.ru>
 <CA+55aFycGSrN27gP4kh6eLZdkSxFvVqS8cZn1YJairD3+z3Zpg@mail.gmail.com>
 <55CCE8A3.7020105@list.ru>
 <CALCETrWW9-Nv=cnHu5gM5QjXCb0NeQkZ=ScnUONpTv2c=1aXwQ@mail.gmail.com>
 <55CCEC6C.3000800@list.ru>
 <CA+55aFzeA+kVgEV+OZn6L3=kX4V9YuErmw+Z0X6A+CGzM4fiFA@mail.gmail.com>
 <55CCF733.70507@list.ru>
 <CA+55aFxJiKe55hB_xiVrrwCunGnzKme7g9VdEBsAcPhNpf9p-A@mail.gmail.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
        Linux kernel <linux-kernel@vger.kernel.org>
From: Stas Sergeev <stsp@list.ru>
Message-ID: <55D2D35A.7040608@list.ru>
Date: Tue, 18 Aug 2015 09:40:26 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <CA+55aFxJiKe55hB_xiVrrwCunGnzKme7g9VdEBsAcPhNpf9p-A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mras: Ok
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

13.08.2015 23:07, Linus Torvalds пишет:
> On Thu, Aug 13, 2015 at 12:59 PM, Stas Sergeev <stsp@list.ru> wrote:
>> It doesn't: fedora provides a "sanitized up" version of sigcontext.h
>> in /usr/include/bits, which comes from glibc-headers-2.21-7.fc22.x86_64.
>> So it seems the "sanitized up" headers come from glibc, which
>> means all other distros would have that too.
> Yes. Except the whole point of uapi was that in the long term the
> glibc people should just be able to pick up the kernel ones directly.
>
> And while that may involve some further editing, it sure as hell
> shouldn't involve "oh, I know, this got renamed, so now I have to
> rename it back". That would be crazy.
Of course they shouldn't rename back, but the breakage in
this case will be seen only to the upstream authors and the
distributors who compile the package, but never to the end-user.
They'll just quickly release the update without troubling the user.
This way kernel could force the uapi changes without too
much troubles, and, for example, when it stopped to use
.fs/.fs fields for FS/GS, it could actually reasonably do that.