Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp5625309pxb; Mon, 28 Mar 2022 15:08:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzD7xdCgVsrXvFikXFbh8mGanhrLkiH5LFQSw1l5qONj1OydPKnE4wFeRgMh83XCzz72bef X-Received: by 2002:a05:620a:4508:b0:67d:c137:68df with SMTP id t8-20020a05620a450800b0067dc13768dfmr17992890qkp.337.1648505307548; Mon, 28 Mar 2022 15:08:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648505307; cv=none; d=google.com; s=arc-20160816; b=cFBvZ7R79V1r9fo2FgkmrDqcpqkK/lC7tXl2ftGPkiX2di2aug/U3AOT+qW/R3NHc3 AxZhrER6BBba7RhKMPLqUwyM6M5GN/e/8j62GxyjyVi7iZY7zMoasodwVJTd1mfIDHhU YPRti+NthKTLdMgOujNXXdu5pRG6OXzs9xSlewrFEp/F+JnpB4NGfuhdtHpBfyMnWaEM UwU5Mvj95w9qzaHpRDHgJAHDjopzKyirABHPecR114VUzsP+Wm+uZ7kYRFcF9W04vTxe VHAsYCENnBPBF1unQo2umvdqONUbg8jKrr1bWtsVIKyI/mhz0I+d303zFTppyNKz1KKj VGIQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=8Gd1mrZiQOq3smqLlHqwKW871rQ12hCh1YJ0GNZOHYE=; b=BEle2TuqjwIJCw23tuYtvFIXZsqNAMIBt1dfUGv79aVTP0HPZ/veAmPQF5IpHkcX0R 9D7zmUQeqdqe6hDUnr/93AhHrNy+w1bYjaOY56UH31Ibo0Zp3OKUYnLk5cBes53Q8afH VOVzLuoQi+EH4HU75m2rADwFF2KFIq+k20QLLUDxHaMw0mY3M7/IBch7m6bLx+Vgj3ik wRPeiQNM6Ei5dTWU3DvUk1lOXspW2c6VFJagAwwuBz7MHPbXq4q8WJSY+SVvUQ/WTXlA YIyVtUXUbfJZ1pzd+oYItSgXQwFd5EYPUwimzslZnBzoeRnColQ4gcgIXLcRWAGOXxsX m2sA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=TrjSxQqo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id u2-20020a1f6002000000b0033fdcc39b3bsi3143426vkb.124.2022.03.28.15.08.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Mar 2022 15:08:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=TrjSxQqo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 943FF14D7B5; Mon, 28 Mar 2022 14:29:33 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240740AbiC1QD0 (ORCPT + 99 others); Mon, 28 Mar 2022 12:03:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39922 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238088AbiC1QDY (ORCPT ); Mon, 28 Mar 2022 12:03:24 -0400 Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F186226ADF for ; Mon, 28 Mar 2022 09:01:43 -0700 (PDT) Received: by mail-pg1-x530.google.com with SMTP id b130so11159229pga.13 for ; Mon, 28 Mar 2022 09:01:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=8Gd1mrZiQOq3smqLlHqwKW871rQ12hCh1YJ0GNZOHYE=; b=TrjSxQqoq2V/zaVRUVmSd509ZbzvmP9G/rPfqEw958xRKal/oCddaFt9mZTwpiStt6 T7i7jI0YEJ+bPWHPrOL6wm2UbnQsGp/BhD272MaNjuRcndS5qKCbDC9pKTu3Lhvkdjcy nVhO+/vDMFl+S+YlrJm74pvhlS92O00zdMHRg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=8Gd1mrZiQOq3smqLlHqwKW871rQ12hCh1YJ0GNZOHYE=; b=8CUhhivQgr+uUScMLUqYIkqEBMPomikk+qHgxPETLD4KMGMvn2x5RfxONQp3+L1fgE V59shLl5TptBTEkKgyNMcSrVNJN5e2f6JVsmEnRq00JT2k3VG1zNbFWe+nW++BShMFxR COc/99TNmFVJuylHJtcDWrtAd1kPwZamjg5usAiDYszwyWQc25IuS+0rIP1N4TZfGm9z H5HC6l3eLo3e06TOdIF5OKzZJfvbtBv9+iBfCqLq9L3IZwGk7nuAn93Vk+gSuw8O/Ccj 6nJR/2Hu5Fdt2rtnCD/O+zMHdgPWkuuFjJtVv6+vBxecP2snyZT0iukT86ncGZTYChBA xaGA== X-Gm-Message-State: AOAM5326/s6hX9IthjONZwBC6pDOcqdo5/8FjbPKyUloD35vS0gXanAr AWlqbtzmWqPmxhH3PGSpxfw2Z2F8A4fsLw== X-Received: by 2002:a05:6a00:2402:b0:4e1:46ca:68bd with SMTP id z2-20020a056a00240200b004e146ca68bdmr23889175pfh.70.1648483303527; Mon, 28 Mar 2022 09:01:43 -0700 (PDT) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id 124-20020a621682000000b004f6a2e59a4dsm16262776pfw.121.2022.03.28.09.01.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Mar 2022 09:01:43 -0700 (PDT) Date: Mon, 28 Mar 2022 09:01:42 -0700 From: Kees Cook To: Linus Torvalds Cc: Linux Kernel Mailing List , George Burgess IV , linux-hardening@vger.kernel.org, llvm@lists.linux.dev, Miguel Ojeda , Nathan Chancellor , Nick Desaulniers Subject: Re: [GIT PULL] FORTIFY_SOURCE updates for v5.18-rc1 Message-ID: <202203280854.C36F2EC@keescook> References: <202203251443.9BBADFD98@keescook> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 26, 2022 at 12:40:18PM -0700, Linus Torvalds wrote: > On Sat, Mar 26, 2022 at 12:29 PM Linus Torvalds > wrote: > > > > Because if all the compiler issues and warnings have been sorted out, > > it sounds to me like the compile-time side could/should be done > > unconditionally if there are no runtime downsides. Yeah, I'd like to do this. The way the header files are currently split up makes this slightly weird, and there have been issues with some arch/compiler combinations, so it's not quite as cut-and-dried as I'd like. I'll investigate what it could look like. > .. or do the existing compiler warnings for the builtins already cover > all cases, and the only reason the fortify-source code has > compile-time warnings is that the option takes over the builtins? This mostly depends on the compiler version, and they often overlap, but the new FORTIFY logic tends to be more strict (where possible) and is more consistent; I view the two diagnostic capabilities as complementary. -- Kees Cook