From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754218AbdEIB6f (ORCPT ); Mon, 8 May 2017 21:58:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47534 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751908AbdEIB6d (ORCPT ); Mon, 8 May 2017 21:58:33 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 9C981C049D57 Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jpoimboe@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 9C981C049D57 Date: Mon, 8 May 2017 20:58:29 -0500 From: Josh Poimboeuf To: Kees Cook Cc: LKML , Peter Zijlstra , PaX Team , Jann Horn , Eric Biggers , Christoph Hellwig , "axboe@kernel.dk" , James Bottomley , Elena Reshetova , Hans Liljestrand , David Windsor , "x86@kernel.org" , Ingo Molnar , Arnd Bergmann , Greg Kroah-Hartman , "David S. Miller" , Rik van Riel , linux-arch , "kernel-hardening@lists.openwall.com" Subject: Re: [PATCH v3 2/2] x86/refcount: Implement fast refcount overflow protection Message-ID: <20170509015829.iycvxxbyblfgklsg@treble> References: <1494271972-140319-1-git-send-email-keescook@chromium.org> <1494271972-140319-3-git-send-email-keescook@chromium.org> <20170508225308.a6uznrhdm7pgyhcg@treble> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Tue, 09 May 2017 01:58:33 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 08, 2017 at 04:31:11PM -0700, Kees Cook wrote: > On Mon, May 8, 2017 at 3:53 PM, Josh Poimboeuf wrote: > > On Mon, May 08, 2017 at 12:32:52PM -0700, Kees Cook wrote: > >> +#define REFCOUNT_EXCEPTION \ > >> + "movl $0x7fffffff, %[counter]\n\t" \ > >> + "int $"__stringify(X86_REFCOUNT_VECTOR)"\n" \ > >> + "0:\n\t" \ > >> + _ASM_EXTABLE(0b, 0b) > > > > Despite the objtool warnings going away, this still uses the exception > > table in a new way, which will confuse objtool. I need to do some more > > thinking about the best way to fix it, either as a change to your patch > > or a change to objtool. > > In that it's not a "true" exception? Right. And also that it doesn't need the "fixup" since it would return to the same address anyway. -- Josh