From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D169EC47247 for ; Tue, 5 May 2020 22:37:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A5DCA20721 for ; Tue, 5 May 2020 22:37:56 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="fc+sEK//" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729569AbgEEWh4 (ORCPT ); Tue, 5 May 2020 18:37:56 -0400 Received: from mail.zx2c4.com ([192.95.5.64]:33133 "EHLO mail.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728076AbgEEWhz (ORCPT ); Tue, 5 May 2020 18:37:55 -0400 Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 4b5e7785; Tue, 5 May 2020 22:25:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=zx2c4.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; s=mail; bh=Xmrp5mSypaMdXoDD21AWMvUQLus=; b=fc+sEK //aogbYTSnnJAa80R+/LMD8vukObNf9opqJQXd2VaPOoMoRsTeakuZvT0o9+D5Tu UD4jB5fJVHwIAHoxMTenKkJxjPiW/0k+P4oKIooUldnok21aj7L+qGunOg687ddE TVbdzT/8e48NqQ+hTIA/wJ9kWI3QDW4GdPVOKs+giK+rfJNeeGX8JEDZv9ff2Zky 0KLKIoyUT1kXlfXzuCMjCLLJovE2jqvNhgGZnLMIFftqvzdKuyY/18tRkThV1bcm j2uyWJdlgNW8yDMmAxXX18HaNWxLbvpDJfQqohwkbZISVO1/2W0c2uMc5nmMt4vh ikvqLkY4fLHi/fag== Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 0f08cdc9 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 5 May 2020 22:25:14 +0000 (UTC) Received: by mail-io1-f51.google.com with SMTP id f3so225622ioj.1; Tue, 05 May 2020 15:37:49 -0700 (PDT) X-Gm-Message-State: AGi0PubvjxrCIApRoy6usn/dZmjZ0nX5wN6heE9AMYBqRHFIgNkL2uPV Ne6kEirxVEhd/g6gh1KXaEBdr4cXHJUnI9CF6r4= X-Google-Smtp-Source: APiQypIMXHaVA0r53/yu3ohly0KqV9mHBNiR3J+yG56KaFKXdRY80P72wnCldnOEX/2Yawf4pZEuzWOZ1K7cea8YJO8= X-Received: by 2002:a02:b88e:: with SMTP id p14mr5651739jam.36.1588718269082; Tue, 05 May 2020 15:37:49 -0700 (PDT) MIME-Version: 1.0 References: <20200505215503.691205-1-Jason@zx2c4.com> <20200505222540.GA230458@ubuntu-s3-xlarge-x86> In-Reply-To: <20200505222540.GA230458@ubuntu-s3-xlarge-x86> From: "Jason A. Donenfeld" Date: Tue, 5 May 2020 16:37:38 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] Kbuild: disable FORTIFY_SOURCE on clang-10 To: Nathan Chancellor Cc: Nick Desaulniers , "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , LKML , clang-built-linux , Arnd Bergmann , Kees Cook , George Burgess Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 5, 2020 at 4:25 PM Nathan Chancellor wrote: > I believe these issues are one in the same. I did a reverse bisect with > Arnd's test case and converged on George's first patch: > > https://github.com/llvm/llvm-project/commit/2dd17ff08165e6118e70f00e22b2c36d2d4e0a9a > > I think that in lieu of this patch, we should have that patch and its > follow-up fix merged into 10.0.1. If this is fixed in 10.0.1, do we even need to patch the kernel at all? Or can we just leave it be, considering most organizations using clang know what they're getting into? I'd personally prefer the latter, so that we don't clutter things.