From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197]) by kanga.kvack.org (Postfix) with ESMTP id 19B936B000A for ; Mon, 30 Jul 2018 12:40:12 -0400 (EDT) Received: by mail-lj1-f197.google.com with SMTP id z24-v6so2820661lji.16 for ; Mon, 30 Jul 2018 09:40:12 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id d192-v6sor1136550lfd.176.2018.07.30.09.40.07 for (Google Transport Security); Mon, 30 Jul 2018 09:40:08 -0700 (PDT) MIME-Version: 1.0 Reply-To: sedat.dilek@gmail.com In-Reply-To: References: <20180730091934.omn2vj6eyh6kaecs@lakrids.cambridge.arm.com> <20180730094622.av7wlyrkl3rn37mp@lakrids.cambridge.arm.com> From: Sedat Dilek Date: Mon, 30 Jul 2018 18:40:06 +0200 Message-ID: Subject: Re: [llvmlinux] clang fails on linux-next since commit 8bf705d13039 Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Nick Desaulniers Cc: Mark Rutland , Matthias Kaehlcke , Dmitry Vyukov , Greg Hackmann , Luis Lozano , Michael Davidson , Paul Lawrence , Sami Tolvanen , kasan-dev , Ingo Molnar , Linux Memory Management List , llvmlinux@lists.linuxfoundation.org, sil2review@lists.osadl.org, JBeulich@suse.com, Peter Zijlstra , Kees Cook , Colin Ian King On Mon, Jul 30, 2018 at 6:35 PM, Nick Desaulniers wrote: > On Mon, Jul 30, 2018 at 2:46 AM Mark Rutland wrote: >> >> On Mon, Jul 30, 2018 at 11:40:49AM +0200, Sedat Dilek wrote: >> > What are your plans to have... >> > >> > 4d2b25f630c7 locking/atomics: Instrument cmpxchg_double*() >> > f9881cc43b11 locking/atomics: Instrument xchg() >> > df79ed2c0643 locking/atomics: Simplify cmpxchg() instrumentation >> > 00d5551cc4ee locking/atomics/x86: Reduce arch_cmpxchg64*() instrumentation >> > >> > ...for example in Linux 4.18 or 4.17.y? >> >> I have no plans to have these backported. > > If they help us compile with clang, we'll backport to 4.17, 4.14, 4.9, > and 4.4 stable. From > https://github.com/ClangBuiltLinux/linux/issues/3#issuecomment-408839428, > it sounds like that is the case. > I am doing a CONFIG_HARDENED_USERCOPY=n build right now and see tommorow if it boots on bare metal. - sed@ -