Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754366AbaFXVSJ (ORCPT ); Tue, 24 Jun 2014 17:18:09 -0400 Received: from mail.skyhub.de ([78.46.96.112]:60565 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751419AbaFXVSG (ORCPT ); Tue, 24 Jun 2014 17:18:06 -0400 Date: Tue, 24 Jun 2014 23:18:02 +0200 From: Borislav Petkov To: Andy Lutomirski Cc: "H. Peter Anvin" , Richard Weinberger , X86 ML , Eric Paris , Linux Kernel , "security@kernel.org" , Steven Rostedt , Toralf =?utf-8?Q?F=C3=B6rster?= , stable , Roland McGrath Subject: Re: [PATCH] x86_32,entry: Do syscall exit work on badsys (CVE-2014-4508) Message-ID: <20140624211802.GC15068@pd.tnic> References: <20140624105108.GG4439@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 24, 2014 at 01:53:25PM -0700, Andy Lutomirski wrote: > It confirms my sense that no one knows how to test this stuff :-/ > It's pretty clear that no one has ever extensively hammered it. Someone might've known at some point but who knows who knew. :-) > I wonder how much could be effectively rewritten in C. I'm thinking of > redoing most of the entry work in C, but that won't help here. Whatever you do, you'll have to do testing yourself, I'm afraid, here too. And then, after the patch is long committed and forgotten, someone would resurface complaining that it breaks some obscure use case. Eeh, the sad life of a kernel developer. :-\ -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- 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/