From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6 1/1] include/trace/hooks/fs.h:19:1: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Sun, 26 Oct 2025 02:33:08 +0800 [thread overview]
Message-ID: <202510260243.qWRKALoV-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android15-6.6
head: cf7e6e9ee1a5d1be5002e412a58ed3a45bb8e892
commit: 29429c25a600ea41fc44db5d8de0f65bce2872ac [1/1] ANDROID: vendor_hooks: add hooks for f2fs down read
config: x86_64-randconfig-121-20251025 (https://download.01.org/0day-ci/archive/20251026/202510260243.qWRKALoV-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/20251026/202510260243.qWRKALoV-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/202510260243.qWRKALoV-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/f2fs/checkpoint.c: note: in included file:
>> include/trace/hooks/fs.h:19:1: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct tracepoint_func *it_func_ptr @@ got struct tracepoint_func [noderef] __rcu *funcs @@
include/trace/hooks/fs.h:19:1: sparse: expected struct tracepoint_func *it_func_ptr
include/trace/hooks/fs.h:19:1: sparse: got struct tracepoint_func [noderef] __rcu *funcs
vim +19 include/trace/hooks/fs.h
11
12 DECLARE_RESTRICTED_HOOK(android_rvh_ksys_umount,
13 TP_PROTO(char __user *name, int flags),
14 TP_ARGS(name, flags), 1);
15 DECLARE_HOOK(android_vh_f2fs_file_open,
16 TP_PROTO(struct inode *inode, struct file *filp),
17 TP_ARGS(inode, filp));
18
> 19 DECLARE_RESTRICTED_HOOK(android_rvh_f2fs_down_read,
20 TP_PROTO(wait_queue_head_t *read_waiters, struct rw_semaphore *rwsem, bool *skip),
21 TP_ARGS(read_waiters, rwsem, skip), 1);
22
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-10-25 18:34 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=202510260243.qWRKALoV-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@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.