From: kernel test robot <lkp@intel.com>
To: Ibrahim Jirdeh <ibrahimjirdeh@meta.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
jack@suse.cz, amir73il@gmail.com, josef@toxicpanda.com,
lesha@meta.com, linux-fsdevel@vger.kernel.org, sargun@meta.com
Subject: Re: [PATCH v4 3/3] fanotify: introduce event response identifier
Date: Sun, 13 Jul 2025 04:51:40 +0800 [thread overview]
Message-ID: <202507130418.Prp26RtQ-lkp@intel.com> (raw)
In-Reply-To: <20250711183101.4074140-4-ibrahimjirdeh@meta.com>
Hi Ibrahim,
kernel test robot noticed the following build errors:
[auto build test ERROR on jack-fs/fsnotify]
[also build test ERROR on linus/master v6.16-rc5 next-20250711]
[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/Ibrahim-Jirdeh/fanotify-add-support-for-a-variable-length-permission-event/20250712-023425
base: https://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify
patch link: https://lore.kernel.org/r/20250711183101.4074140-4-ibrahimjirdeh%40meta.com
patch subject: [PATCH v4 3/3] fanotify: introduce event response identifier
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20250713/202507130418.Prp26RtQ-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250713/202507130418.Prp26RtQ-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/202507130418.Prp26RtQ-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/notify/fdinfo.c:17:
>> fs/notify/fanotify/fanotify.h:566:6: error: no member named 'fanotify_data' in 'struct fsnotify_group'
566 | if (FAN_GROUP_FLAG(group, FAN_REPORT_RESPONSE_ID))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/fanotify.h:9:12: note: expanded from macro 'FAN_GROUP_FLAG'
9 | ((group)->fanotify_data.flags & (flag))
| ~~~~~~~ ^
1 error generated.
vim +566 fs/notify/fanotify/fanotify.h
562
563 static inline bool fanotify_is_valid_response_id(struct fsnotify_group *group,
564 int id)
565 {
> 566 if (FAN_GROUP_FLAG(group, FAN_REPORT_RESPONSE_ID))
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-12 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 18:30 [PATCH v4 0/3] fanotify: introduce response identifier Ibrahim Jirdeh
2025-07-11 18:30 ` [PATCH v4 1/3] fanotify: add support for a variable length permission event Ibrahim Jirdeh
2025-07-22 14:01 ` Jan Kara
2025-07-22 15:13 ` Amir Goldstein
2025-07-23 7:43 ` Jan Kara
2025-07-23 10:24 ` Amir Goldstein
2025-07-11 18:31 ` [PATCH v4 2/3] fanotify: allow pre-content events with fid info Ibrahim Jirdeh
2025-07-11 18:31 ` [PATCH v4 3/3] fanotify: introduce event response identifier Ibrahim Jirdeh
2025-07-12 6:16 ` Amir Goldstein
2025-07-12 20:51 ` kernel test robot [this message]
2025-07-16 6:25 ` 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=202507130418.Prp26RtQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=ibrahimjirdeh@meta.com \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=lesha@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sargun@meta.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;
as well as URLs for NNTP newsgroup(s).