From: kernel test robot <lkp@intel.com>
To: Song Liu <song@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [song:fanotify-bpf 1/3] fs/notify/fanotify/fanotify.c:1062:63: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Wed, 06 May 2026 14:17:42 +0800 [thread overview]
Message-ID: <202605061408.WGETFhTu-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/song/linux.git fanotify-bpf
head: d2202d928a9b4a190058b1bc4731b72477a10c8e
commit: 85c87cab4c9c2ffa4a9d2b00525a75576f50c550 [1/3] fanotify: Introduce fanotify filter
config: nios2-randconfig-r133-20260506 (https://download.01.org/0day-ci/archive/20260506/202605061408.WGETFhTu-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260506/202605061408.WGETFhTu-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/202605061408.WGETFhTu-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/notify/fanotify/fanotify.c:1062:63: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct fanotify_filter_hook *filter_hook @@ got struct fanotify_filter_hook [noderef] __rcu *filter_hook @@
fs/notify/fanotify/fanotify.c:1062:63: sparse: expected struct fanotify_filter_hook *filter_hook
fs/notify/fanotify/fanotify.c:1062:63: sparse: got struct fanotify_filter_hook [noderef] __rcu *filter_hook
vim +1062 fs/notify/fanotify/fanotify.c
1048
1049 static void fanotify_free_group_priv(struct fsnotify_group *group)
1050 {
1051 put_user_ns(group->user_ns);
1052 kfree(group->fanotify_data.merge_hash);
1053 if (group->fanotify_data.ucounts)
1054 dec_ucount(group->fanotify_data.ucounts,
1055 UCOUNT_FANOTIFY_GROUPS);
1056
1057 if (mempool_initialized(&group->fanotify_data.error_events_pool))
1058 mempool_exit(&group->fanotify_data.error_events_pool);
1059
1060 #ifdef CONFIG_FANOTIFY_FILTER
1061 if (group->fanotify_data.filter_hook)
> 1062 fanotify_filter_hook_free(group->fanotify_data.filter_hook);
1063 #endif
1064 }
1065
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-06 6:17 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=202605061408.WGETFhTu-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=song@kernel.org \
/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.