Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp1559618ybj; Fri, 8 May 2020 04:19:33 -0700 (PDT) X-Google-Smtp-Source: APiQypIzOMGGr2b2sNPjTilL0feOEUpylCgxUQ+aTB5ALQVHUUdnejunN+aj109dz5ouCrq9+JhR X-Received: by 2002:a50:88a6:: with SMTP id d35mr1675971edd.238.1588936773652; Fri, 08 May 2020 04:19:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588936773; cv=none; d=google.com; s=arc-20160816; b=fd2p68I1tpqfHj9bci8XsewZ/H+Kg5wliHcuCqRdTcOUkThmGYgIbiIkxJ/VNGiDr+ 0mnaHahpX/Y5gg/ytWAF10XELiOHMm+3WdqS74oThbdjZrkGZYEl9SDeyRTmLgVwS9k9 OKND6qaleTTpfH2bdxIK9uwYBvJXHt40MfOsmdytQx/xfd1CuHSjNxStYj05gaAPYIxu K5FHKUDfPO+G5gErVALQWNopdi1W5bPEBAsj0hm9siITvF9i+tEjoqH1+FU8ESD1EtBZ EqAc61sfzn1/Q2+pB6ZFOUUThxGaKXcfdKHq/8i+hVBCpuAWIPxj+CqjXoT3H6M5qbs5 RU5g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=05yejxlqG112oAiJcuXsV6RzSLjBiSOJw5IfNxYWv1M=; b=aKvpYsIRnUl/My20he8WSb9thexkPwsPqqGHq4FVFnJKgALlu9mQB7E1JCnqhOe63J K9I34J2bHW4FdDBoRRK2S4mLDmnKli/mgUM0mzktJg9p0DdzQr4T0rrkYM1isisqbpTW PWEJKVu8PdiAMoBtMd45U4+1uThjmh84fHUpdIwU6/V7k59+XnEAXDHBI0WgNjLLyuSj ZMH5gzoXZ9VfIalkFIHyBxrIdFz5nu6i+FzsxE+VdrhqIawgczdbA+bKJSq87StZrn9X Y+khcj/Nq2LqmT1YQXrh7pwF/dKoA1n0O7F0cGyvlfT1z5dxl3dbotuCPXhCFGB9kZFr tLnA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JwiGw3nb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u8si743078eds.295.2020.05.08.04.19.11; Fri, 08 May 2020 04:19:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JwiGw3nb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727113AbgEHLRU (ORCPT + 99 others); Fri, 8 May 2020 07:17:20 -0400 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:26347 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726792AbgEHLRU (ORCPT ); Fri, 8 May 2020 07:17:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1588936638; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=05yejxlqG112oAiJcuXsV6RzSLjBiSOJw5IfNxYWv1M=; b=JwiGw3nbXDuxXyg3t7wMggOazzBjmzo0NtTysF4pl+kjyuki+/xpKvcOJWvYMBI+Rs/A8q Fil/4WUu3EXo/f3PEvy9jiN2kMPpqyNl4yIp/Q1b3SAzS7QGRLrHQ556oUtpKoyznnVsFr x+NbSBgnqWrKrOgjDHpQBH686QnmoDI= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-441-6s15L47gOZeCdQrWo-lI9A-1; Fri, 08 May 2020 07:17:14 -0400 X-MC-Unique: 6s15L47gOZeCdQrWo-lI9A-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 57A49107ACF2; Fri, 8 May 2020 11:17:13 +0000 (UTC) Received: from madcap2.tricolour.ca (unknown [10.3.128.9]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B66526155F; Fri, 8 May 2020 11:17:03 +0000 (UTC) Date: Fri, 8 May 2020 07:17:00 -0400 From: Richard Guy Briggs To: "Gustavo A. R. Silva" Cc: Paul Moore , Eric Paris , linux-audit@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] audit: Replace zero-length array with flexible-array Message-ID: <20200508111700.4uwa7oizxqakbk3t@madcap2.tricolour.ca> References: <20200507185041.GA13930@embeddedor> <20200507215812.ksvwcykfged7ye2a@madcap2.tricolour.ca> <20200507224955.GA22343@embeddedor> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200507224955.GA22343@embeddedor> User-Agent: NeoMutt/20180716 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-05-07 17:49, Gustavo A. R. Silva wrote: > On Thu, May 07, 2020 at 05:58:13PM -0400, Richard Guy Briggs wrote: > > On 2020-05-07 13:50, Gustavo A. R. Silva wrote: > > > The current codebase makes use of the zero-length array language > > > extension to the C90 standard, but the preferred mechanism to declare > > > variable-length types such as these ones is a flexible array member[1][2], > > > introduced in C99: > > > > > > struct foo { > > > int stuff; > > > struct boo array[]; > > > }; > > > > > > By making use of the mechanism above, we will get a compiler warning > > > in case the flexible array does not occur last in the structure, which > > > will help us prevent some kind of undefined behavior bugs from being > > > inadvertently introduced[3] to the codebase from now on. > > > > > > Also, notice that, dynamic memory allocations won't be affected by > > > this change: > > > > > > "Flexible array members have incomplete type, and so the sizeof operator > > > may not be applied. As a quirk of the original implementation of > > > zero-length arrays, sizeof evaluates to zero."[1] > > > > > > sizeof(flexible-array-member) triggers a warning because flexible array > > > members have incomplete type[1]. There are some instances of code in > > > which the sizeof operator is being incorrectly/erroneously applied to > > > zero-length arrays and the result is zero. Such instances may be hiding > > > some bugs. So, this work (flexible-array member conversions) will also > > > help to get completely rid of those sorts of issues. > > > > > > This issue was found with the help of Coccinelle. > > > > > > [1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html > > > [2] https://github.com/KSPP/linux/issues/21 > > > [3] commit 76497732932f ("cxgb3/l2t: Fix undefined behaviour") > > > > > > Signed-off-by: Gustavo A. R. Silva > > > > Sounds reasonable to me. There's another in include/uapi/linux/audit.h > > Hi, Hello Gustavo, > I wouldn't advise to make any of these conversions in include/uapi/ > [1][2]. Ah-hah. Thanks for the contra-indicating supporting references. > > in struct audit_rule_data buf[0]. This alert also helped me fix another > > one in a patchset I'm about to post (and will probably cause a merge > > conflict but we can figure that out). > > Awesome. :) > > > Reviewed-by: Richard Guy Briggs > > Thanks > -- > Gustavo > > [1] https://lore.kernel.org/lkml/20200424121553.GE26002@ziepe.ca/ > [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1e6e9d0f4859ec698d55381ea26f4136eff3afe1 > > > > --- > > > include/linux/audit.h | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > diff --git a/include/linux/audit.h b/include/linux/audit.h > > > index f9ceae57ca8d..2b63aee6e9fa 100644 > > > --- a/include/linux/audit.h > > > +++ b/include/linux/audit.h > > > @@ -19,7 +19,7 @@ > > > struct audit_sig_info { > > > uid_t uid; > > > pid_t pid; > > > - char ctx[0]; > > > + char ctx[]; > > > }; > > > > > > struct audit_buffer; > > > > - RGB - RGB -- Richard Guy Briggs Sr. S/W Engineer, Kernel Security, Base Operating Systems Remote, Ottawa, Red Hat Canada IRC: rgb, SunRaycer Voice: +1.647.777.2635, Internal: (81) 32635