From: kernel test robot <lkp@intel.com>
To: Song Liu <song@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC bpf-next fanotify 4/5] fanotify: Enable bpf based fanotify fastpath handler
Date: Sat, 2 Nov 2024 13:02:02 +0800 [thread overview]
Message-ID: <202411021247.TwBBZ3ZJ-lkp@intel.com> (raw)
In-Reply-To: <20241029231244.2834368-5-song@kernel.org>
Hi Song,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf/master]
[also build test ERROR on jack-fs/fsnotify linus/master v6.12-rc5]
[cannot apply to bpf-next/master next-20241101]
[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/Song-Liu/fanotify-Introduce-fanotify-fastpath-handler/20241030-071530
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
patch link: https://lore.kernel.org/r/20241029231244.2834368-5-song%40kernel.org
patch subject: [RFC bpf-next fanotify 4/5] fanotify: Enable bpf based fanotify fastpath handler
config: i386-randconfig-016-20241102 (https://download.01.org/0day-ci/archive/20241102/202411021247.TwBBZ3ZJ-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241102/202411021247.TwBBZ3ZJ-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/202411021247.TwBBZ3ZJ-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/notify/fanotify/fanotify_fastpath.c: In function 'bpf_fanotify_fastpath_is_valid_access':
>> fs/notify/fanotify/fanotify_fastpath.c:217:14: error: implicit declaration of function 'bpf_tracing_btf_ctx_access' [-Werror=implicit-function-declaration]
217 | if (!bpf_tracing_btf_ctx_access(off, size, type, prog, info))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from fs/notify/fanotify/fanotify_fastpath.c:4:
fs/notify/fanotify/fanotify_fastpath.c: In function 'bpf_fanotify_fastpath_struct_ops_init':
include/linux/bpf.h:1868:50: warning: statement with no effect [-Wunused-value]
1868 | #define register_bpf_struct_ops(st_ops, type) ({ (void *)(st_ops); 0; })
| ^~~~~~~~~~~~~~~~
fs/notify/fanotify/fanotify_fastpath.c:315:22: note: in expansion of macro 'register_bpf_struct_ops'
315 | ret = ret ?: register_bpf_struct_ops(&bpf_fanotify_fastpath_ops, fanotify_fastpath_ops);
| ^~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/bpf_tracing_btf_ctx_access +217 fs/notify/fanotify/fanotify_fastpath.c
211
212 static bool bpf_fanotify_fastpath_is_valid_access(int off, int size,
213 enum bpf_access_type type,
214 const struct bpf_prog *prog,
215 struct bpf_insn_access_aux *info)
216 {
> 217 if (!bpf_tracing_btf_ctx_access(off, size, type, prog, info))
218 return false;
219
220 return true;
221 }
222
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-02 5:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 23:12 [RFC bpf-next fanotify 0/5] Fanotify fastpath handler Song Liu
2024-10-29 23:12 ` [RFC bpf-next fanotify 1/5] fanotify: Introduce fanotify " Song Liu
2024-10-30 12:45 ` Jeff Layton
2024-11-07 10:48 ` Jan Kara
2024-11-07 19:13 ` Song Liu
2024-11-11 14:09 ` Jan Kara
2024-10-29 23:12 ` [RFC bpf-next fanotify 2/5] samples/fanotify: Add a sample " Song Liu
2024-10-30 0:11 ` Al Viro
2024-10-30 1:48 ` Al Viro
2024-10-30 2:07 ` Song Liu
2024-10-30 2:35 ` Song Liu
2024-10-30 13:03 ` Jeff Layton
2024-10-30 20:30 ` Song Liu
2024-10-31 0:23 ` Jeff Layton
2024-10-31 1:52 ` Song Liu
2024-11-06 19:40 ` Amir Goldstein
2024-11-06 22:10 ` Song Liu
2024-11-07 10:41 ` Jan Kara
2024-11-07 19:39 ` Song Liu
2024-11-07 11:19 ` Amir Goldstein
2024-11-07 19:39 ` Song Liu
2024-11-02 2:57 ` kernel test robot
2024-10-29 23:12 ` [RFC bpf-next fanotify 3/5] bpf: Make bpf inode storage available to tracing programs Song Liu
2024-10-29 23:12 ` [RFC bpf-next fanotify 4/5] fanotify: Enable bpf based fanotify fastpath handler Song Liu
2024-11-02 5:02 ` kernel test robot [this message]
2024-11-02 5:23 ` kernel test robot
2024-10-29 23:12 ` [RFC bpf-next fanotify 5/5] selftests/bpf: Add test for BPF " Song Liu
2024-11-07 11:10 ` Amir Goldstein
2024-11-07 19:53 ` Song Liu
2024-11-07 20:33 ` Amir Goldstein
2024-11-07 20:48 ` Song Liu
2024-11-08 8:18 ` Amir Goldstein
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=202411021247.TwBBZ3ZJ-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.