Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754675AbcCJJn6 (ORCPT ); Thu, 10 Mar 2016 04:43:58 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:33278 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754555AbcCJJno (ORCPT ); Thu, 10 Mar 2016 04:43:44 -0500 Date: Thu, 10 Mar 2016 10:43:39 +0100 From: Ingo Molnar To: Jonathan Corbet Cc: Scotty Bauer , linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com, x86@kernel.org, wmealing@redhat.com, ak@linux.intel.com, luto@amacapital.net, Abhiram Balasubramanian , Linus Torvalds Subject: Re: [PATCH v3 1/3] SROP Mitigation: Architecture independent code for signal cookies Message-ID: <20160310094339.GA5105@gmail.com> References: <1457470075-4586-1-git-send-email-sbauer@eng.utah.edu> <20160309083204.GA30365@gmail.com> <56E09E8B.1010909@eng.utah.edu> <20160309152212.07a9b83b@lwn.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160309152212.07a9b83b@lwn.net> 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 Content-Length: 1310 Lines: 38 * Jonathan Corbet wrote: > On Wed, 9 Mar 2016 15:07:07 -0700 > Scotty Bauer wrote: > > > On 03/09/2016 01:32 AM, Ingo Molnar wrote: > > > > > > Could you please add a high level description in Documentation > > > that explains the attack and the way how this mitigation code > > > prevents that kind of attack? > > > > > > Also, the first changelogs should contain more high level > > > description as well. For example, what does the 'verification' > > > of the signal cookie mean, and how does it prevent an SROP > > > attempt? > > > > > > All of these patches seem to assume that people reading this code > > > know what SROP is and how we defend against it - that is not so. > > > > I'm going to submit v4 to fix some nits where I'll include the explanation > > and a change log, I apologize for not doing that here. In the meantime if > > you don't mind visiting a link I included a brief explanation on previous > > versions of the patch set. > > > > https://lkml.org/lkml/2016/2/6/166 > > The curious might also find background information in my article about this > patch set: > > https://lwn.net/Articles/676803/ Scott, mind including a prominent link to the (excellent!) LWN.net article in the changelog/documentation as well? Thanks, Ingo