From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754084AbdKISzD (ORCPT ); Thu, 9 Nov 2017 13:55:03 -0500 Received: from mail-io0-f178.google.com ([209.85.223.178]:47214 "EHLO mail-io0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752517AbdKISzB (ORCPT ); Thu, 9 Nov 2017 13:55:01 -0500 X-Google-Smtp-Source: AGs4zMaWdb8EhSCA6Hg4IyJArzUoIKSN6uFwm2wBWDwKNzao1x0ilMHBg2fNtgIkZ2FbPAoTquqhaA== Date: Thu, 9 Nov 2017 10:54:57 -0800 From: Sami Tolvanen To: Ard Biesheuvel Cc: "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Matthias Kaehlcke , Nick Desaulniers , Kees Cook , Greg Hackmann Subject: Re: [PATCH 10/15] arm64: disable ARM64_ERRATUM_843419 for clang LTO Message-ID: <20171109185457.GA137560@samitolvanen.mtv.corp.google.com> References: <20171103171203.107569-1-samitolvanen@google.com> <20171103171203.107569-12-samitolvanen@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 03, 2017 at 08:13:20PM +0000, Ard Biesheuvel wrote: > I wonder it makes sense to disable such relocations entirely when we > enable this erratum. If the toolchain does not generate them, they > shouldn't occur in the first place, and having this dependency here > seems awkward as well. I agree. Unless someone objects, I'll replace this in v2 with a patch that leaves the relocations in module.c even when the erratum is selected. Sami