From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
Subject: [boqun:shazptr-v2 4/8] kernel/locking/shazptr.c:134:25-30: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)
Date: Wed, 19 Nov 2025 00:04:12 +0800 [thread overview]
Message-ID: <202511190017.SU1AkQK2-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Boqun Feng <boqun.feng@gmail.com>
CC: "Paul E. McKenney" <paulmck@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git shazptr-v2
head: 904b8eaf21a993852b97d086d8d7a21916090cb9
commit: 31a43aa06d630ad79d471b02aee3348e369e6ba8 [4/8] shazptr: Avoid synchronize_shaptr() busy waiting
:::::: branch date: 25 hours ago
:::::: commit date: 25 hours ago
config: xtensa-randconfig-r053-20251118 (https://download.01.org/0day-ci/archive/20251119/202511190017.SU1AkQK2-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 10.5.0
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/202511190017.SU1AkQK2-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> kernel/locking/shazptr.c:134:25-30: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)
vim +134 kernel/locking/shazptr.c
31a43aa06d630a Boqun Feng 2025-04-13 122
31a43aa06d630a Boqun Feng 2025-04-13 123 /* Scan structure for synchronize_shazptr(). */
31a43aa06d630a Boqun Feng 2025-04-13 124 struct shazptr_scan {
31a43aa06d630a Boqun Feng 2025-04-13 125 struct task_struct *thread;
31a43aa06d630a Boqun Feng 2025-04-13 126 struct swait_queue_head wq;
31a43aa06d630a Boqun Feng 2025-04-13 127 struct list_head scanning;
31a43aa06d630a Boqun Feng 2025-04-13 128 int cpu_grp_size;
31a43aa06d630a Boqun Feng 2025-04-13 129
31a43aa06d630a Boqun Feng 2025-04-13 130 struct mutex lock;
31a43aa06d630a Boqun Feng 2025-04-13 131 struct list_head queued; /* __guard_by(lock) */
31a43aa06d630a Boqun Feng 2025-04-13 132 bool scheduled; /* __guard_by(lock) */
31a43aa06d630a Boqun Feng 2025-04-13 133
31a43aa06d630a Boqun Feng 2025-04-13 @134 struct shazptr_snapshot snaps[0]; /* __counted_by(nr_cpu_ids) */
31a43aa06d630a Boqun Feng 2025-04-13 135 };
31a43aa06d630a Boqun Feng 2025-04-13 136
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-18 16:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202511190017.SU1AkQK2-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.