Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753688AbbHMSfn (ORCPT ); Thu, 13 Aug 2015 14:35:43 -0400 Received: from mail-ig0-f174.google.com ([209.85.213.174]:36843 "EHLO mail-ig0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752767AbbHMSfm (ORCPT ); Thu, 13 Aug 2015 14:35:42 -0400 MIME-Version: 1.0 In-Reply-To: <55CCD921.4040301@list.ru> References: <55CA90B4.2010205@list.ru> <55CCD921.4040301@list.ru> Date: Thu, 13 Aug 2015 11:35:41 -0700 X-Google-Sender-Auth: 1ivNmj9RWmKmff7MwrBX7mn4LHc Message-ID: Subject: Re: [regression] x86/signal/64: Fix SS handling for signals delivered to 64-bit programs breaks dosemu From: Linus Torvalds To: Stas Sergeev Cc: Andy Lutomirski , Linux kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1261 Lines: 28 On Thu, Aug 13, 2015 at 10:51 AM, Stas Sergeev wrote: > > Hello Linus, I verified that patch-minimal.diff is enough > to fix the problem, BUT! dosemu is in fact using the .fs and > .gs fields of sigcontext as a placeholders. Why the minimal > patch alone helps is simply because the kernel headers > installed in a system do not yet represent the newer kernel > developments and have the .fs and .gs fields in. Ok. So I'm inclined to do the bigger revert, just to fix the compile issue. It would be crazy to force some silly autoconf script for random header info. Of course, we could also just let the uabi version go out of sync with the internal version, but that sounds even worse. I think we'd be better off just leaving the old names, and just having big comments about this.. Andy? I agree that we should strive to improve in this area, and this should be worked on, but that would seem to be a 4.3 issue (and mark that too for stable once it actually works). No? Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/