Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757198Ab3DXPjV (ORCPT ); Wed, 24 Apr 2013 11:39:21 -0400 Received: from mail-we0-f172.google.com ([74.125.82.172]:45341 "EHLO mail-we0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755733Ab3DXPjT (ORCPT ); Wed, 24 Apr 2013 11:39:19 -0400 Date: Wed, 24 Apr 2013 17:39:15 +0200 From: Frederic Weisbecker To: Oleg Nesterov Cc: Jiri Olsa , linux-kernel@vger.kernel.org, Thomas Gleixner , "H. Peter Anvin" , Andi Kleen , Arnaldo Carvalho de Melo , Peter Zijlstra , Ingo Molnar , Paul Mackerras , Corey Ashford , Vince Weaver , Stephane Eranian Subject: Re: [PATCH 1/6] signal x86: Propage RF EFLAGS bit throught the signal restore call Message-ID: <20130424153914.GC6993@somewhere> References: <1362940871-24486-1-git-send-email-jolsa@redhat.com> <1362940871-24486-2-git-send-email-jolsa@redhat.com> <20130416010524.GH17561@somewhere.redhat.com> <20130416144226.GA12848@redhat.com> <20130417200206.GA18253@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130417200206.GA18253@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1655 Lines: 44 On Wed, Apr 17, 2013 at 10:02:06PM +0200, Oleg Nesterov wrote: > On 04/16, Oleg Nesterov wrote: > > > > On 04/16, Frederic Weisbecker wrote: > > > > > > On Sun, Mar 10, 2013 at 07:41:06PM +0100, Jiri Olsa wrote: > > > > Adding RF EFLAGS bit to be restored on return from signal from > > > > the original register context before the signal was entered. > > > > > > > > This will prevent the RF flag to disappear when returning > > > > from exception due to the signal handler being executed. > > > > > > So that happens if, say, we get a breakpoint exception and then we > > > run a signal handler before returning to the ip that triggered the > > > breakpoint? > > > > Afaics these changes (1 and 2) should fix the bug. > > > > Suppose that the first insn in the signal handler should trigger > > another bp, we should clear X86_EFLAGS_RF (2/6). > > > > Otoh, we should restore it when we return to the original insn > > which triggered the trap to avoid another trap. > > I applied 1 and 2, and this fixes the test-case below. > > > But. it seems that we have yet another problem? Suppose that > > the signal handler does siglongjmp() and jumps to yet another > > insn which should trigger the trap? > > Argh. Sorry for confusion. I tried to say that the signal handler > can play with sigcontext->ip before sigreturn(). But probably we > can ignore this. Hmm, ok. Anyway patches 1-3 look good! Thanks! -- 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/