From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754118AbbHMTtm (ORCPT ); Thu, 13 Aug 2015 15:49:42 -0400 Received: from mail-oi0-f54.google.com ([209.85.218.54]:36306 "EHLO mail-oi0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752879AbbHMTtl convert rfc822-to-8bit (ORCPT ); Thu, 13 Aug 2015 15:49:41 -0400 MIME-Version: 1.0 In-Reply-To: <55CCEA73.1030403@list.ru> References: <55CA90B4.2010205@list.ru> <55CCD921.4040301@list.ru> <55CCEA73.1030403@list.ru> From: Andy Lutomirski Date: Thu, 13 Aug 2015 12:49:20 -0700 Message-ID: Subject: Re: [regression] x86/signal/64: Fix SS handling for signals delivered to 64-bit programs breaks dosemu To: Stas Sergeev Cc: "linux-kernel@vger.kernel.org" , Linus Torvalds Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Aug 13, 2015 12:05 PM, "Stas Sergeev" wrote: > > 13.08.2015 21:41, Andy Lutomirski пишет: > >> Stas: I think uc_flags is okay. We don't currently read it during >> sigreturn, but I see no reason that we can't start reading it. > > Andy, we definitely have some communication discontinuity here. :) > The point is not sigreturn. If we are talking about the flags that > will in the future control also TLS, how would you limit it to sigreturn()? > It should control the restoring of FS _on signal delivery_, not only > on sigreturn()! So how uc_flags can be used for this at all? Ah, you want it restored on signal delivery. What would it be restored to? ISTM that can be done easily enough in user code, so maybe we should leave it to user code. --Andy