From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
Subject: kernel/bpf/dmabuf_iter.c:109:7-15: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)
Date: Tue, 24 Mar 2026 01:20:29 +0800 [thread overview]
Message-ID: <202603240106.OB40altv-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: "T.J. Mercier" <tjmercier@google.com>
CC: Alexei Starovoitov <ast@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c369299895a591d96745d6492d4888259b004a9e
commit: 6eab7ac7c5eea7628b92cd5f9427bbd963a954ec bpf: Add open coded dmabuf iterator
date: 10 months ago
:::::: branch date: 20 hours ago
:::::: commit date: 10 months ago
config: s390-randconfig-r051-20260323 (https://download.01.org/0day-ci/archive/20260324/202603240106.OB40altv-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project c911b8492374942bf4cfe35411e90a35d3837f6a)
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/202603240106.OB40altv-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> kernel/bpf/dmabuf_iter.c:109:7-15: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)
vim +109 kernel/bpf/dmabuf_iter.c
6eab7ac7c5eea7 T.J. Mercier 2025-05-22 103
6eab7ac7c5eea7 T.J. Mercier 2025-05-22 104 struct bpf_iter_dmabuf {
6eab7ac7c5eea7 T.J. Mercier 2025-05-22 105 /*
6eab7ac7c5eea7 T.J. Mercier 2025-05-22 106 * opaque iterator state; having __u64 here allows to preserve correct
6eab7ac7c5eea7 T.J. Mercier 2025-05-22 107 * alignment requirements in vmlinux.h, generated from BTF
6eab7ac7c5eea7 T.J. Mercier 2025-05-22 108 */
6eab7ac7c5eea7 T.J. Mercier 2025-05-22 @109 __u64 __opaque[1];
6eab7ac7c5eea7 T.J. Mercier 2025-05-22 110 } __aligned(8);
6eab7ac7c5eea7 T.J. Mercier 2025-05-22 111
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-03-23 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 17:20 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-05 14:15 kernel/bpf/dmabuf_iter.c:109:7-15: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays) kernel test robot
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=202603240106.OB40altv-lkp@intel.com \
--to=lkp@intel.com \
--cc=julia.lawall@inria.fr \
--cc=oe-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.