Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp3543984iog; Mon, 27 Jun 2022 19:31:09 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tSzPym7mopEXVPVmbvMwOI46045yeiueI8vVOE2tMOaqsOdcAn7pQLzAi3goMrQdSlp1SJ X-Received: by 2002:a17:902:dac5:b0:16a:7560:2ad1 with SMTP id q5-20020a170902dac500b0016a75602ad1mr2517258plx.168.1656383468814; Mon, 27 Jun 2022 19:31:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656383468; cv=none; d=google.com; s=arc-20160816; b=NJu/YDI9l8YAbwZqe8s33i797D28rw2WHB9eGyIsl8LUSyRXzg2l0+Rx9Em80xWe93 Cml9gp2ZSQrPKttip4L0sDn+p/faEvdnLcXO1kpeETG6pMEeRFDa0mpyhw484if0VN/4 AXgL4rB5pvz6P6gPEYD2BdJ4mbiGYmEaTjuc/L48F+K12iFLCiZnHTzXJM82ZZ6U7HF8 5FufeNlUI1tc+ZNXmbqdjMXeFatRdAK3uZMWJaWcR5MPp1KRkDghlObidM6dHDhYHmD/ fT/taR8ZAc4pmCS1fGW9gBEEhObrKISjFlRnDgQJLTw6aXFdOhVZjLn8gZ+ZFY+Rq6cw KdPQ== 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-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=ulqk+cEaNXHl50r0UfdEglq/v3UovGtRCwIRozCeJc8=; b=mKn0fQpeBkKzaCBB4sFFYXm60+Mn3OEh8HzXVoA45khF9kDY+TLpet/HIYliye/imx 2Cxc5UFg3/8F+LJ7O5w7paRx/WBb5LTBgyQ0JfPNYRyxX8Vxqa2/Uu9iqlPauJk46R5R xexLn3LRlrcbrE7vYBNOChsf2hpI2t4BaKKNyqNqM61L/0lCTOBa4ra3Cf96Wy9Z808e 5NBNhPz39akaWe6/BK1J7gRyWjia2GIq1ldYL/u29fmTsR+Pf4ttZaI0vEx5yrqvCfPw 83YOcZlFz+kWBGTv3QsQDMJYg9OBT7GQl5g/n/Pvi6HsjUbzbO5wnYKUh9r82yt7/mx4 eWdg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=GyqsByaD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u193-20020a6279ca000000b00522c3a00ee9si15974964pfc.270.2022.06.27.19.30.56; Mon, 27 Jun 2022 19:31:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=GyqsByaD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243985AbiF1CXL (ORCPT + 99 others); Mon, 27 Jun 2022 22:23:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60944 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243804AbiF1CWB (ORCPT ); Mon, 27 Jun 2022 22:22:01 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6B476248F4; Mon, 27 Jun 2022 19:21:37 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 26F64B818E4; Tue, 28 Jun 2022 02:21:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id F3298C341CB; Tue, 28 Jun 2022 02:21:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1656382894; bh=pqPD6qoEi8JT199in7jg5DAol4iF8DjKFPgIGYlvQoc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=GyqsByaDXQg5yOq6smuSw5cw5zuxTHl+rHrYo/OlHMZ1OuAvd9ONI8/jqrzLdImbD VTWK7UP5itlkHBzyKuMpIHQb6qIkgBzcX3Jxv+GaaOi42Ij7zVfd0aNVRCj/2kEQLZ O6R0SdzzjedD8BThjNur1AhOSXcjIOf8wUfiJdziqd597shekW5NqBhdePKYvvXsYS oJiSFkiCFnaZl7loW+605mJuFv8NTwWJO3O6z94S5MRsftmK5FPbSEThNMZ5b+uoVL ifMihZ1oD6Ug5EuhwczB9HuCayJu7LpnnMklqlMLvNn/Nf3BKVwwKkKVP3/5TDDlCW d3gJG/ZMvv/2g== Date: Tue, 28 Jun 2022 04:21:29 +0200 From: "Gustavo A. R. Silva" To: Jason Gunthorpe Cc: Daniel Borkmann , Kees Cook , linux-kernel@vger.kernel.org, x86@kernel.org, dm-devel@redhat.com, linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org, linux-s390@vger.kernel.org, kvm@vger.kernel.org, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, netdev@vger.kernel.org, bpf@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-can@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux1394-devel@lists.sourceforge.net, io-uring@vger.kernel.org, lvs-devel@vger.kernel.org, linux-mtd@lists.infradead.org, kasan-dev@googlegroups.com, linux-mmc@vger.kernel.org, nvdimm@lists.linux.dev, netfilter-devel@vger.kernel.org, coreteam@netfilter.org, linux-perf-users@vger.kernel.org, linux-raid@vger.kernel.org, linux-sctp@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-scsi@vger.kernel.org, target-devel@vger.kernel.org, linux-usb@vger.kernel.org, virtualization@lists.linux-foundation.org, v9fs-developer@lists.sourceforge.net, linux-rdma@vger.kernel.org, alsa-devel@alsa-project.org, linux-hardening@vger.kernel.org Subject: Re: [PATCH][next] treewide: uapi: Replace zero-length arrays with flexible-array members Message-ID: <20220628022129.GA8452@embeddedor> References: <20220627180432.GA136081@embeddedor> <6bc1e94c-ce1d-a074-7d0c-8dbe6ce22637@iogearbox.net> <20220628004052.GM23621@ziepe.ca> <20220628005825.GA161566@embeddedor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220628005825.GA161566@embeddedor> X-Spam-Status: No, score=-7.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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 Tue, Jun 28, 2022 at 02:58:25AM +0200, Gustavo A. R. Silva wrote: > On Mon, Jun 27, 2022 at 09:40:52PM -0300, Jason Gunthorpe wrote: > > On Mon, Jun 27, 2022 at 08:27:37PM +0200, Daniel Borkmann wrote: > > > On 6/27/22 8:04 PM, Gustavo A. R. Silva wrote: > > > > There is a regular need in the kernel to provide a way to declare > > > > having a dynamically sized set of trailing elements in a structure. > > > > Kernel code should always use “flexible array members”[1] for these > > > > cases. The older style of one-element or zero-length arrays should > > > > no longer be used[2]. > > > > > > > > This code was transformed with the help of Coccinelle: > > > > (linux-5.19-rc2$ spatch --jobs $(getconf _NPROCESSORS_ONLN) --sp-file script.cocci --include-headers --dir . > output.patch) > > > > > > > > @@ > > > > identifier S, member, array; > > > > type T1, T2; > > > > @@ > > > > > > > > struct S { > > > > ... > > > > T1 member; > > > > T2 array[ > > > > - 0 > > > > ]; > > > > }; > > > > > > > > -fstrict-flex-arrays=3 is coming and we need to land these changes > > > > to prevent issues like these in the short future: > > > > > > > > ../fs/minix/dir.c:337:3: warning: 'strcpy' will always overflow; destination buffer has size 0, > > > > but the source string has length 2 (including NUL byte) [-Wfortify-source] > > > > strcpy(de3->name, "."); > > > > ^ > > > > > > > > Since these are all [0] to [] changes, the risk to UAPI is nearly zero. If > > > > this breaks anything, we can use a union with a new member name. > > > > > > > > [1] https://en.wikipedia.org/wiki/Flexible_array_member > > > > [2] https://www.kernel.org/doc/html/v5.16/process/deprecated.html#zero-length-and-one-element-arrays > > > > > > > > Link: https://github.com/KSPP/linux/issues/78 > > > > Build-tested-by: https://lore.kernel.org/lkml/62b675ec.wKX6AOZ6cbE71vtF%25lkp@intel.com/ > > > > Signed-off-by: Gustavo A. R. Silva > > > > --- > > > > Hi all! > > > > > > > > JFYI: I'm adding this to my -next tree. :) > > > > > > Fyi, this breaks BPF CI: > > > > > > https://github.com/kernel-patches/bpf/runs/7078719372?check_suite_focus=true > > > > > > [...] > > > progs/map_ptr_kern.c:314:26: error: field 'trie_key' with variable sized type 'struct bpf_lpm_trie_key' not at the end of a struct or class is a GNU extension [-Werror,-Wgnu-variable-sized-type-not-at-end] > > > struct bpf_lpm_trie_key trie_key; > > > ^ > > > > This will break the rdma-core userspace as well, with a similar > > error: > > > > /usr/bin/clang-13 -DVERBS_DEBUG -Dibverbs_EXPORTS -Iinclude -I/usr/include/libnl3 -I/usr/include/drm -g -O2 -fdebug-prefix-map=/__w/1/s=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wmissing-prototypes -Wmissing-declarations -Wwrite-strings -Wformat=2 -Wcast-function-type -Wformat-nonliteral -Wdate-time -Wnested-externs -Wshadow -Wstrict-prototypes -Wold-style-definition -Werror -Wredundant-decls -g -fPIC -std=gnu11 -MD -MT libibverbs/CMakeFiles/ibverbs.dir/cmd_flow.c.o -MF libibverbs/CMakeFiles/ibverbs.dir/cmd_flow.c.o.d -o libibverbs/CMakeFiles/ibverbs.dir/cmd_flow.c.o -c ../libibverbs/cmd_flow.c > > In file included from ../libibverbs/cmd_flow.c:33: > > In file included from include/infiniband/cmd_write.h:36: > > In file included from include/infiniband/cmd_ioctl.h:41: > > In file included from include/infiniband/verbs.h:48: > > In file included from include/infiniband/verbs_api.h:66: > > In file included from include/infiniband/ib_user_ioctl_verbs.h:38: > > include/rdma/ib_user_verbs.h:436:34: error: field 'base' with variable sized type 'struct ib_uverbs_create_cq_resp' not at the end of a struct or class is a GNU extension [-Werror,-Wgnu-variable-sized-type-not-at-end] > > struct ib_uverbs_create_cq_resp base; > > ^ > > include/rdma/ib_user_verbs.h:644:34: error: field 'base' with variable sized type 'struct ib_uverbs_create_qp_resp' not at the end of a struct or class is a GNU extension [-Werror,-Wgnu-variable-sized-type-not-at-end] > > struct ib_uverbs_create_qp_resp base; > > > > Which is why I gave up trying to change these.. > > > > Though maybe we could just switch off -Wgnu-variable-sized-type-not-at-end during configuration ? > > No. I think now we can easily workaround these sorts of problems with > something like this: > > struct flex { > any_type any_member; > union { > type array[0]; > __DECLARE_FLEX_ARRAY(type, array_flex); > }; > }; Mmmh... nope; this doesn't work[1]. We need to think in a different strategy. -- Gustavo [1] https://godbolt.org/z/av79Pqbfz