cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: gfs2@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [Cluster-devel] [gfs2:extents 14/14] fs/gfs2/extents.c:123:23-27: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays) (fwd)
Date: Thu, 19 Oct 2023 13:28:13 +0100	[thread overview]
Message-ID: <be0ce0c5-5278-4d29-94d2-e5ce26e8e3b5@redhat.com> (raw)
In-Reply-To: <a8791f89-ed7b-1649-3b53-72349899c5d@inria.fr>

On 19/10/2023 06:27, Julia Lawall wrote:
> 
> 
> ---------- Forwarded message ----------
> Date: Thu, 19 Oct 2023 05:56:44 +0800
> From: kernel test robot <lkp@intel.com>
> To: oe-kbuild@lists.linux.dev
> Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
> Subject: [gfs2:extents 14/14] fs/gfs2/extents.c:123:23-27: WARNING use
>      flexible-array member instead
>      (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-
>      and-one-element-arrays)
> 
> BCC: lkp@intel.com
> CC: oe-kbuild-all@lists.linux.dev
> CC: cluster-devel@redhat.com

The lkp-tests contact info is out of date. I've opened a PR to fix it at 
https://github.com/intel/lkp-tests/pull/319 but it should probably use 
the latest MAINTAINERS file always. CCing the new gfs2 list.

Thanks,
Andy

> TO: Andreas Gruenbacher <agruenba@redhat.com>
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git extents
> head:   86474c69cac46872bd311318c02fb8e9e25abd10
> commit: 86474c69cac46872bd311318c02fb8e9e25abd10 [14/14] gfs2: Add some initial extents-based inode code
> :::::: branch date: 9 days ago
> :::::: commit date: 9 days ago
> config: x86_64-randconfig-101-20231018 (https://download.01.org/0day-ci/archive/20231019/202310190541.0impmnL4-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce: (https://download.01.org/0day-ci/archive/20231019/202310190541.0impmnL4-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Reported-by: Julia Lawall <julia.lawall@inria.fr>
> | Closes: https://lore.kernel.org/r/202310190541.0impmnL4-lkp@intel.com/
> 
> cocci warnings: (new ones prefixed by >>)
>>> fs/gfs2/extents.c:123:23-27: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)
> 
> vim +123 fs/gfs2/extents.c
> 
> 86474c69cac468 Andreas Gruenbacher 2021-03-25  115
> 86474c69cac468 Andreas Gruenbacher 2021-03-25  116  /*
> 86474c69cac468 Andreas Gruenbacher 2021-03-25  117   * The path components in struct gfs2_extent_path are stored in "reverse"
> 86474c69cac468 Andreas Gruenbacher 2021-03-25  118   * order: the leaf is stored first, and when the tree grows at the root,
> 86474c69cac468 Andreas Gruenbacher 2021-03-25  119   * this happens at the end of the array.
> 86474c69cac468 Andreas Gruenbacher 2021-03-25  120   */
> 86474c69cac468 Andreas Gruenbacher 2021-03-25  121  struct gfs2_extent_path {
> 86474c69cac468 Andreas Gruenbacher 2021-03-25  122  	unsigned int p_height;
> 86474c69cac468 Andreas Gruenbacher 2021-03-25 @123  	struct gfs2_extent_pc p_pc[1];
> 86474c69cac468 Andreas Gruenbacher 2021-03-25  124  };
> 86474c69cac468 Andreas Gruenbacher 2021-03-25  125
> 


      reply	other threads:[~2023-10-20  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  5:27 [Cluster-devel] [gfs2:extents 14/14] fs/gfs2/extents.c:123:23-27: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays) (fwd) Julia Lawall
2023-10-19 12:28 ` Andrew Price [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=be0ce0c5-5278-4d29-94d2-e5ce26e8e3b5@redhat.com \
    --to=anprice@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --cc=julia.lawall@inria.fr \
    --cc=oe-kbuild-all@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).