Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752178AbdHIUcr (ORCPT ); Wed, 9 Aug 2017 16:32:47 -0400 Received: from mail-yw0-f177.google.com ([209.85.161.177]:36191 "EHLO mail-yw0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752001AbdHIUco (ORCPT ); Wed, 9 Aug 2017 16:32:44 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Kostya Serebryany Date: Wed, 9 Aug 2017 13:32:42 -0700 Message-ID: Subject: Re: new ELF marking To: "H.J. Lu" Cc: Kees Cook , LKML , Binutils Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 694 Lines: 21 > > > > I believe this would only be an output bit, but I'm not sure how it > > would be wired into binutils. Kostya, do you know any details about > > how AddressSanitizer might be able to create this ELF note? I don't, hopefully H.J's suggestion works. Will it be backward compatible? (i.e. will the binaries built in the new way work on the old kernels?) Thanks! --kcc > > > if it is an output only bit, "-z fobar" should work, like > > -z ibt Generate GNU_PROPERTY_X86_FEATURE_1_IBT > -z shstk Generate GNU_PROPERTY_X86_FEATURE_1_SHSTK > > Or you can put it in the input file and linker will copy it to output, like > GNU_PROPERTY_STACK_SIZE.