From: Florian Weimer Subject: Re: [PATCH] binfmt_elf: Extract .note.gnu.property from an ELF file Date: Thu, 27 Jun 2019 11:38:45 +0200 Message-ID: <87ef3fweoq.fsf@oldenburg2.str.redhat.com> References: <20190501211217.5039-1-yu-cheng.yu@intel.com> <20190502111003.GO3567@e103592.cambridge.arm.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: (Andy Lutomirski's message of "Wed, 26 Jun 2019 10:14:07 -0700") Sender: linux-kernel-owner@vger.kernel.org To: Andy Lutomirski Cc: Dave Martin , Yu-cheng Yu , X86 ML , "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , LKML , "open list:DOCUMENTATION" , Linux-MM , linux-arch , Linux API , Arnd Bergmann , Balbir Singh , Cyrill Gorcunov , Dave Hansen , Eugene Syromiatnikov , "H.J. Lu" , Jann Horn , Jonathan Corbet , Kees Cook , Mike Kravetz List-Id: linux-api@vger.kernel.org * Andy Lutomirski: > Also, I don't think there's any actual requirement that the upstream > kernel recognize existing CET-enabled RHEL 8 binaries as being > CET-enabled. I tend to think that RHEL 8 jumped the gun here. The ABI was supposed to be finalized and everyone involved thought it had been reviewed by the GNU gABI community and other interested parties. It had been included in binutils for several releases. >From my point of view, the kernel is just a consumer of the ABI. The kernel would not change an instruction encoding if it doesn't like it for some reason, either. > While the upstream kernel should make some reasonble effort to make > sure that RHEL 8 binaries will continue to run, I don't see why we > need to go out of our way to keep the full set of mitigations > available for binaries that were developed against a non-upstream > kernel. They were developed against the ABI specification. I do not have a strong opinion what the kernel should do going forward. I just want to make clear what happened. Thanks, Florian