From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752031AbdHaRUK convert rfc822-to-8bit (ORCPT ); Thu, 31 Aug 2017 13:20:10 -0400 Received: from mout.gmx.net ([212.227.15.19]:56097 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751823AbdHaRUH (ORCPT ); Thu, 31 Aug 2017 13:20:07 -0400 Message-ID: <1504199967.666.16.camel@gmx.de> Subject: Re: tip -ENOBOOT - bisected to locking/refcounts, x86/asm: Implement fast refcount overflow protection From: Mike Galbraith To: Kees Cook Cc: "David S. Miller" , Peter Zijlstra , LKML , Ingo Molnar , "Reshetova, Elena" , Network Development Date: Thu, 31 Aug 2017 19:19:27 +0200 In-Reply-To: References: <1503996623.8323.20.camel@gmx.de> <1504025721.6024.25.camel@gmx.de> <1504030207.6560.0.camel@gmx.de> <1504069332.8352.3.camel@gmx.de> <1504113212.5852.6.camel@gmx.de> <1504115735.5852.11.camel@gmx.de> <1504145389.23109.4.camel@gmx.de> <1504149176.23109.9.camel@gmx.de> <1504187918.27500.16.camel@gmx.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 Mime-Version: 1.0 Content-Transfer-Encoding: 8BIT X-Provags-ID: V03:K0:HAg2QoanjeCD21KvYWsUTTsgWwPjWzWwB2snVE+vVaIWTX9Exos oilhQURPsN3EBkc7p2Q0zQGy0nj9hTtxvlTEf0KepUf58geCeaQOs11U/mgqTGhJ4U96G0V AkvccL0Z2qR6MogpxCVOTPjH6mSP5fAk+sZFniwEnmmRgR9eS0Xl1E2wWYC5U+WY2sH6IZl EwcRV0hYyiPRJZpAkS9/w== X-UI-Out-Filterresults: notjunk:1;V01:K0:4ttAiczoHcU=:0stOWJjvXUgw66RVQswVbK 907zMSJtOOAotxjB3upfvWIrfMERNnj6KfsKsWLTZ3X0jEw68upaQCT1P8W6DQ1SiLGa09WuC FyjlVxEkQrN1WnF9h4kjIvTa09bGJwGxTkKh+N9QgXLa67tAy6GwYEXemap0tbZiaVldlEjBp fqx7jTXjcAP3nlr5tLqOOmrepIgB+zWb8zAwYzC8NlCdZe2ZMb5DEhWdOgZV4T5SgPfkzFzfF S8zV7SCHOBB2W5MDoIaA45qiyA1Z/GNa4BRVsPLn+11gr+vl1Z774ZvyFiK+vPdXdySarDqwh RuTz/jv+8o88e9j/lU4OF6+UhndwjBHZpL5SE8uMP63B3ixFgKmSX/0gf/bXoDWTPXEM1W7Bj e3RXj5aF7BdaZo1MZTamOoLyrC9p/QLXRIFqG0kwupoF79HifkZqPYpIRzWbo9ZymdvAGrita RfrJt2p8tpk4JXoSxlFSrSlEZSB1shOKPJFTH9keFVtIdiua6g9orTg3qNZb5fab04g92UPUS lUrUIr0sheOnJ+5bLpEzUOaQOxRagdwVp5GM+nu5YqsQUMoANMRUzaZD4lZTPaYLF1oTYMXcp uyDi1BVbM9+sHlKe2dv3wqbIcX0DkLaWXwGlv3LGiKzTouyAkQAvPhx6sf/7OXWDW73dBO/MJ p0a9zhiBde53l7UlhBS2d6Q7I8E//qxY0XxAxqQZ+18yDii4qaq/oGGBgIkZv9mTgHF8H/hpZ PSbmqPb/LZVOelSRgn2+5nSpPsThWFalVdGAH0krJ3EpLk4bNRy44M4bh4TukhWZX7Mt5mvFi 5Yr9P2lTBvty2wXJW+p7EHl4SXJJJy4nwdSM07YBhjR/OubxhY= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2017-08-31 at 10:00 -0700, Kees Cook wrote: > > Oh! So it's gcc-version sensitive? That's alarming. Is this mapping correct: > > 4.8.5: WARN, eventual kernel hang > 6.3.1, 7.0.1: WARN, but continues working Yeah, that's correct.  I find that troubling, simply because this gcc version has been through one hell of a lot of kernels with me.  Yeah, I know, that doesn't exempt it from having bugs, but color me suspicious. -Mike