From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1757520AbcAaVqi (ORCPT <rfc822;w@1wt.eu>);
	Sun, 31 Jan 2016 16:46:38 -0500
Received: from mail.skyhub.de ([78.46.96.112]:37610 "EHLO mail.skyhub.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1757390AbcAaVqh (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sun, 31 Jan 2016 16:46:37 -0500
Date: Sun, 31 Jan 2016 22:46:26 +0100
From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
        Brian Gerst <brgerst@gmail.com>
Subject: Re: [PATCH 0/3] x86/entry/64: Fixes for syscall rework
Message-ID: <20160131214626.GF22584@pd.tnic>
References: <cover.1454261517.git.luto@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <cover.1454261517.git.luto@kernel.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sun, Jan 31, 2016 at 09:33:25AM -0800, Andy Lutomirski wrote:
> I broke iopl(2) with my syscall rework.  Fix it up.  While debugging
> it, I found a bug in my IRQ state handling.  Fix that, too.
> 
> Andy Lutomirski (3):
>   x86/entry/64: Fix an IRQ state error on ptregs-using syscalls
>   x86/entry/64: Fix fast-path syscall return register state
>   x86/syscalls/64: Mark sys_iopl as using ptregs
> 
>  arch/x86/entry/entry_64.S              | 23 ++++++++++++++++-------
>  arch/x86/entry/syscalls/syscall_64.tbl |  2 +-
>  2 files changed, 17 insertions(+), 8 deletions(-)

Looks good so far:

Reported-and-tested-by: Borislav Petkov <bp@suse.de>

We better hammer on those a lot more until the next merge window for
more confidence.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.