Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2054413pxu; Tue, 24 Nov 2020 16:02:06 -0800 (PST) X-Google-Smtp-Source: ABdhPJx2KECwVECt80D1kHrB+ythTPHl1PYBPO9DHy9VOjT6Pq7YVyuMkuEhgDkKclYn846XnOAl X-Received: by 2002:a17:906:af12:: with SMTP id lx18mr876972ejb.324.1606262526585; Tue, 24 Nov 2020 16:02:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606262526; cv=none; d=google.com; s=arc-20160816; b=SDEu0IqP7x2SsszTPDWbUqiw/O5jv/t4BxltAAnx4K/spxCSsAAQC2akRWEGVHfS+G rLIzs92zGli6LdwUfjMnlwwKQ1kH404sV5fLVs1DyX69CxQQgZD1RKtDntBB+smh/BzO S2+ewpk+XbwqIDmWVdVjK/L435hddk+qDYBw7sel75qFXMl2x77UudRky0+ukyOAijAG VA9huzPLIPdHCISP/R7XDj00OdolSuGYBScHhT9AKIVc8DSv/76cig7+4HlAMAf+XMN2 0EgmTzhTwUFg96XHk/uvXo/BvwRCsx+P/m9cBcW314wniQXehGmMV/39bNdBgq92+pRv MFmg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date; bh=rfErvvek2o4mgzvkcpzcQmFb1xIfI/gZvM9qIx9fcLQ=; b=Iv1cQ9ozjPwQYD7cuPCM3kOyz9OWOD55IgbxsFziA26+Ieng6REaAN8c2Hk1lsmBeU S8q7o9PPboN4KWWnJ//UpS+ftbYXSPJczRLWmN3DTmxs5Us3S4+g3IutiVIu11e2OzNJ Xa4fD29yIVrp2yCBzYXozJvmvNgnpdnONns0U3TxTHknSyDhu+N8d3b0U77/q6c4O4+m QLSCk/hvM45MgsQFUTFqrIpO1/trQmeHIkBtpVts5Yy0dyhwDhHrki29fJ3TP5bf3zEf 2fjxVXHEngEXBvmRr7HY1+OTvTaMhrQXjOjYTlzSVkQA48KJJd6o46NGbxswrDOFznw7 ZCcw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hp24si255610ejc.590.2020.11.24.16.01.42; Tue, 24 Nov 2020 16:02:06 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389607AbgKXWYT (ORCPT + 99 others); Tue, 24 Nov 2020 17:24:19 -0500 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:42066 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728076AbgKXWYQ (ORCPT ); Tue, 24 Nov 2020 17:24:16 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by kvm5.telegraphics.com.au (Postfix) with ESMTP id 8A96E22AD6; Tue, 24 Nov 2020 17:24:09 -0500 (EST) Date: Wed, 25 Nov 2020 09:24:08 +1100 (AEDT) From: Finn Thain To: Kees Cook cc: James Bottomley , "Gustavo A. R. Silva" , Joe Perches , Jakub Kicinski , alsa-devel@alsa-project.org, linux-atm-general@lists.sourceforge.net, reiserfs-devel@vger.kernel.org, linux-iio@vger.kernel.org, linux-wireless@vger.kernel.org, linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Nathan Chancellor , linux-ide@vger.kernel.org, dm-devel@redhat.com, keyrings@vger.kernel.org, linux-mtd@lists.infradead.org, GR-everest-linux-l2@marvell.com, wcn36xx@lists.infradead.org, samba-technical@lists.samba.org, linux-i3c@lists.infradead.org, linux1394-devel@lists.sourceforge.net, linux-afs@lists.infradead.org, usb-storage@lists.one-eyed-alien.net, drbd-dev@lists.linbit.com, devel@driverdev.osuosl.org, linux-cifs@vger.kernel.org, rds-devel@oss.oracle.com, Nick Desaulniers , linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org, oss-drivers@netronome.com, bridge@lists.linux-foundation.org, linux-security-module@vger.kernel.org, amd-gfx@lists.freedesktop.org, linux-stm32@st-md-mailman.stormreply.com, cluster-devel@redhat.com, linux-acpi@vger.kernel.org, coreteam@netfilter.org, intel-wired-lan@lists.osuosl.org, linux-input@vger.kernel.org, Miguel Ojeda , tipc-discussion@lists.sourceforge.net, linux-ext4@vger.kernel.org, linux-media@vger.kernel.org, linux-watchdog@vger.kernel.org, selinux@vger.kernel.org, linux-arm-msm@vger.kernel.org, intel-gfx@lists.freedesktop.org, linux-geode@lists.infradead.org, linux-can@vger.kernel.org, linux-block@vger.kernel.org, linux-gpio@vger.kernel.org, op-tee@lists.trustedfirmware.org, linux-mediatek@lists.infradead.org, xen-devel@lists.xenproject.org, nouveau@lists.freedesktop.org, linux-hams@vger.kernel.org, ceph-devel@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-arm-kernel@lists.infradead.org, linux-hwmon@vger.kernel.org, x86@kernel.org, linux-nfs@vger.kernel.org, GR-Linux-NIC-Dev@marvell.com, linux-mm@kvack.org, netdev@vger.kernel.org, linux-decnet-user@lists.sourceforge.net, linux-mmc@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-sctp@vger.kernel.org, linux-usb@vger.kernel.org, netfilter-devel@vger.kernel.org, linux-crypto@vger.kernel.org, patches@opensource.cirrus.com, linux-integrity@vger.kernel.org, target-devel@vger.kernel.org, linux-hardening@vger.kernel.org, Jonathan Cameron , Greg KH Subject: Re: [Intel-wired-lan] [PATCH 000/141] Fix fall-through warnings for Clang In-Reply-To: <202011241327.BB28F12F6@keescook> Message-ID: References: <202011201129.B13FDB3C@keescook> <20201120115142.292999b2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <202011220816.8B6591A@keescook> <9b57fd4914b46f38d54087d75e072d6e947cb56d.camel@HansenPartnership.com> <0147972a72bc13f3629de8a32dee6f1f308994b5.camel@HansenPartnership.com> <20201123130348.GA3119@embeddedor> <8f5611bb015e044fa1c0a48147293923c2d904e4.camel@HansenPartnership.com> <202011241327.BB28F12F6@keescook> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Tue, 24 Nov 2020, Kees Cook wrote: > On Mon, Nov 23, 2020 at 08:31:30AM -0800, James Bottomley wrote: > > Really, no ... something which produces no improvement has no value at > > all ... we really shouldn't be wasting maintainer time with it because > > it has a cost to merge. I'm not sure we understand where the balance > > lies in value vs cost to merge but I am confident in the zero value > > case. > > What? We can't measure how many future bugs aren't introduced because > the kernel requires explicit case flow-control statements for all new > code. > These statements are not "missing" unless you presume that code written before the latest de facto language spec was written should somehow be held to that spec. If the 'fallthrough' statement is not part of the latest draft spec then we should ask why not before we embrace it. Being that the kernel still prefers -std=gnu89 you might want to consider what has prevented -std=gnu99 or -std=gnu2x etc. > We already enable -Wimplicit-fallthrough globally, so that's not the > discussion. The issue is that Clang is (correctly) even more strict than > GCC for this, so these are the remaining ones to fix for full Clang > coverage too. > Seems to me you should be patching the compiler. When you have consensus among the language lawyers you'll have more credibility with those being subjected to enforcement.