Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 17 Feb 2021 10:08:28 -0800
From:   Kees Cook <keescook@chromium.org>
To:     Alexander Lobakin <alobakin@pm.me>
Cc:     Linus Torvalds <torvalds@linux-foundation.org>,
        linux-kernel@vger.kernel.org, Bill Wendling <morbo@google.com>,
        Bjorn Helgaas <bhelgaas@google.com>,
        George Burgess IV <gbiv@google.com>,
        Nick Desaulniers <ndesaulniers@google.com>,
        Sami Tolvanen <samitolvanen@google.com>,
        Steven Rostedt <rostedt@goodmis.org>,
        Will Deacon <will@kernel.org>
Subject: Re: [GIT PULL] clang-lto for v5.12-rc1
Message-ID: <202102171006.DD2F341@keescook>
References: <20210216224751.7367-1-alobakin@pm.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210216224751.7367-1-alobakin@pm.me>
Precedence: bulk

On Tue, Feb 16, 2021 at 10:48:10PM +0000, Alexander Lobakin wrote:
> From: Kees Cook <keescook@chromium.org>
> Date: Tue, 16 Feb 2021 12:34:37 -0800
> 
> > Hi Linus,
> > 
> > Please pull this Clang Link Time Optimization series for v5.12-rc1. This
> > has been in linux-next for the entire last development cycle, and is
> > built on the work done preparing[0] for LTO by arm64 folks, tracing folks,
> > etc. This series includes the core changes as well as the remaining pieces
> > for arm64 (LTO has been the default build method on Android for about
> > 3 years now, as it is the prerequisite for the Control Flow Integrity
> > protections). While x86 LTO support is done[1], there is still some
> > on-going clean-up work happening for objtool[2] that should hopefully
> > land by the v5.13 merge window.
> 
[...]
> 
> Seems like you forgot the fix from [0], didn't you?
> 
[...]
> 
> [0] https://lore.kernel.org/lkml/20210121184544.659998-1-alobakin@pm.me

Ah yes, sorry for overlooking that. I can send a follow-up PR. AIUI,
it's usually better for Linus's workflow for me to build on sent PRs
instead of resending. (But given the merge window disruption, we'll see
what happens!)

-- 
Kees Cook