From: kernel test robot <lkp@intel.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
Jan Kara <jack@suse.cz>, Amir Goldstein <amir73il@gmail.com>,
Matthew Bobrowski <repnop@google.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] fanotify: Avoid a couple of -Wflex-array-member-not-at-end warnings
Date: Thu, 8 May 2025 12:30:06 +0800 [thread overview]
Message-ID: <202505081249.CUDWsu7Z-lkp@intel.com> (raw)
In-Reply-To: <aBqdlxlBtb9s7ydc@kspp>
Hi Gustavo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jack-fs/fsnotify]
[also build test WARNING on linus/master v6.15-rc5 next-20250507]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Gustavo-A-R-Silva/fanotify-Avoid-a-couple-of-Wflex-array-member-not-at-end-warnings/20250507-074110
base: https://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify
patch link: https://lore.kernel.org/r/aBqdlxlBtb9s7ydc%40kspp
patch subject: [PATCH][next] fanotify: Avoid a couple of -Wflex-array-member-not-at-end warnings
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20250508/202505081249.CUDWsu7Z-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250508/202505081249.CUDWsu7Z-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>
| Closes: https://lore.kernel.org/oe-kbuild-all/202505081249.CUDWsu7Z-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from fs/notify/fdinfo.c:17:
>> fs/notify/fanotify/fanotify.h:280:16: warning: alignment 1 of 'union <anonymous>' is less than 4 [-Wpacked-not-aligned]
280 | struct fanotify_fh name; \
| ^~~~~~~~~~~
fs/notify/fanotify/fanotify.h:287:9: note: in expansion of macro 'FANOTIFY_INLINE_FH'
287 | FANOTIFY_INLINE_FH(object_fh, FANOTIFY_INLINE_FH_LEN);
| ^~~~~~~~~~~~~~~~~~
>> fs/notify/fanotify/fanotify.h:280:16: warning: alignment 1 of 'union <anonymous>' is less than 4 [-Wpacked-not-aligned]
280 | struct fanotify_fh name; \
| ^~~~~~~~~~~
fs/notify/fanotify/fanotify.h:315:9: note: in expansion of macro 'FANOTIFY_INLINE_FH'
315 | FANOTIFY_INLINE_FH(object_fh, MAX_HANDLE_SZ);
| ^~~~~~~~~~~~~~~~~~
vim +280 fs/notify/fanotify/fanotify.h
b8a6c3a2f0ae4d Amir Goldstein 2020-07-08 275
2c5069433a3adc Gabriel Krisman Bertazi 2021-10-25 276 #define FANOTIFY_INLINE_FH(name, size) \
e3725b8a2ecdf6 Gustavo A. R. Silva 2025-05-06 277 union { \
e3725b8a2ecdf6 Gustavo A. R. Silva 2025-05-06 278 /* Space for object_fh and object_fh.buf[] - access with fanotify_fh_buf() */ \
e3725b8a2ecdf6 Gustavo A. R. Silva 2025-05-06 279 unsigned char _inline_fh_buf[struct_size_t(struct fanotify_fh, buf, size)]; \
1758cd2e95d31b Alexey Dobriyan 2023-10-10 @280 struct fanotify_fh name; \
e3725b8a2ecdf6 Gustavo A. R. Silva 2025-05-06 281 } __packed
2c5069433a3adc Gabriel Krisman Bertazi 2021-10-25 282
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-05-08 4:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 23:39 [PATCH][next] fanotify: Avoid a couple of -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2025-05-07 5:56 ` Amir Goldstein
2025-05-07 11:08 ` Jan Kara
2025-05-07 17:41 ` Gustavo A. R. Silva
2025-05-08 4:30 ` kernel test robot [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=202505081249.CUDWsu7Z-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=gustavoars@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=repnop@google.com \
/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