From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753930AbaA1BTz (ORCPT ); Mon, 27 Jan 2014 20:19:55 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:44569 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751121AbaA1BTy (ORCPT ); Mon, 27 Jan 2014 20:19:54 -0500 Date: Tue, 28 Jan 2014 01:18:41 +0000 From: Al Viro To: Oleg Nesterov Cc: Peter Zijlstra , Linus Torvalds , Peter Anvin , Ingo Molnar , Thomas Gleixner , the arch/x86 maintainers , Linux Kernel Mailing List Subject: Re: [RFC] de-asmify the x86-64 system call slowpath Message-ID: <20140128011841.GG10323@ZenIV.linux.org.uk> References: <20140127102759.GY11314@laptop.programming.kicks-ass.net> <20140127113627.GC10323@ZenIV.linux.org.uk> <20140127173931.GB32450@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140127173931.GB32450@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 On Mon, Jan 27, 2014 at 06:39:31PM +0100, Oleg Nesterov wrote: > On 01/27, Al Viro wrote: > > > > BTW, there's an additional pile of obfuscation: > > /* work to do on interrupt/exception return */ > > #define _TIF_WORK_MASK \ > > (0x0000FFFF & \ > > ~(_TIF_SYSCALL_TRACE|_TIF_SYSCALL_AUDIT| \ > > _TIF_SINGLESTEP|_TIF_SECCOMP|_TIF_SYSCALL_EMU)) > > > > /* work to do on any return to user space */ > > #define _TIF_ALLWORK_MASK \ > > ((0x0000FFFF & ~_TIF_SECCOMP) | _TIF_SYSCALL_TRACEPOINT | \ > > _TIF_NOHZ) > > Heh, yes ;) > > > Why is _TIF_UPROBE *not* a part > > of _TIF_DO_NOTIFY_MASK, for example? > > Yes, please see another email. That is why uprobe_deny_signal() > sets TIF_NOTIFY_RESUME along with TIF_UPROBE. *grumble* Can it end up modifying *regs? From very cursory reading of kernel/events/uprobe.c it seems to do so, so we probably want to leave via iretq if that has hit, right?