Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754729AbbGXRuy (ORCPT ); Fri, 24 Jul 2015 13:50:54 -0400 Received: from mail-lb0-f176.google.com ([209.85.217.176]:36348 "EHLO mail-lb0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754607AbbGXRuu (ORCPT ); Fri, 24 Jul 2015 13:50:50 -0400 MIME-Version: 1.0 In-Reply-To: <1437745668-31802-2-git-send-email-dvlasenk@redhat.com> References: <1437745668-31802-1-git-send-email-dvlasenk@redhat.com> <1437745668-31802-2-git-send-email-dvlasenk@redhat.com> From: Andy Lutomirski Date: Fri, 24 Jul 2015 10:50:28 -0700 Message-ID: Subject: Re: [PATCH 2/3] x86/asm/entry/32: Remove most of SYSCALL32 code, part 1 To: Denys Vlasenko Cc: Ingo Molnar , Linus Torvalds , "Krzysztof A. Sobiecki" , Steven Rostedt , Borislav Petkov , "H. Peter Anvin" , Oleg Nesterov , Frederic Weisbecker , Alexei Starovoitov , Will Drewry , Kees Cook , X86 ML , "linux-kernel@vger.kernel.org" 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: 965 Lines: 23 On Fri, Jul 24, 2015 at 6:47 AM, Denys Vlasenko wrote: > SYSCALL32 code is nearly identical to SYSCALL32, except for initial > section. Merge them. > > The removal is split into two parts, to make review eaiser. This is part 1. > > auditsys_entry_common and auditsys_exit macros are indented one more tab without > any changes. This prevents diff from becoming unreadable. > They will be removed in part 2. I need to read these more closely, which is, at present, exceeding my ability to look at asm. (See the big NMI thread.) I'll look soon. Meanwhile, this code is incredibly fragile wrt syscall restart. (Syscall restart on compat is really weird.) Do we have a decent test for it? --Andy -- 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/