Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753399AbcKHKhX (ORCPT ); Tue, 8 Nov 2016 05:37:23 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:49293 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752954AbcKHKhQ (ORCPT ); Tue, 8 Nov 2016 05:37:16 -0500 X-ME-Sender: X-Sasl-enc: GRFFAj0IAwoaP6VACIoRxuz66IrdoiKrd0ObL0OMPTWt 1478601417 Date: Tue, 8 Nov 2016 11:36:57 +0100 From: Greg KH To: Linus Torvalds Cc: Jiri Slaby , stable , Linux Kernel Mailing List , Al Viro Subject: Re: [PATCH 3.12 69/72] Revert "fix minor infoleak in get_user_ex()" Message-ID: <20161108103657.GA10689@kroah.com> References: <7c0dfa3b2ea712bd2cc6343445f263815b81918f.1478525307.git.jslaby@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 699 Lines: 17 On Mon, Nov 07, 2016 at 08:45:59AM -0800, Linus Torvalds wrote: > So a patch something like this might be a safe way to fix the > potential infoleak in older kernels. > > THIS IS UNTESTED. It's a very obvious patch, though, so if it compiles > it probably works. It just initializes the output variable with 0 in > the inline asm description, instead of doing it in the exception > handler. > > It will generate slightly worse code (a few unnecessary ALU > operations), but it doesn't have any interactions with the exception > handler implementation. It builds here, so I've queued it up for 4.4-stable, let's see if the auto-builders have any problems with it. Thanks for the patch. greg k-h