From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC bpf-next v1 1/8] bpf: Support pinning in non-bpf file system.
Date: Fri, 07 Jan 2022 08:04:41 +0800 [thread overview]
Message-ID: <202201070824.fU5x5JHr-lkp@intel.com> (raw)
In-Reply-To: <20220106215059.2308931-2-haoluo@google.com>
[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]
Hi Hao,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Hao-Luo/Pinning-bpf-objects-outside-bpffs/20220107-055252
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20220107/202201070824.fU5x5JHr-lkp(a)intel.com/config)
compiler: arceb-elf-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/7c6dacd226b9d48b0c2bcc226bf890776267de90
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Hao-Luo/Pinning-bpf-objects-outside-bpffs/20220107-055252
git checkout 7c6dacd226b9d48b0c2bcc226bf890776267de90
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash kernel/bpf/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> kernel/bpf/inode.c:83:5: warning: no previous prototype for 'handle_inode_event' [-Wmissing-prototypes]
83 | int handle_inode_event(struct fsnotify_mark *mark, u32 mask,
| ^~~~~~~~~~~~~~~~~~
vim +/handle_inode_event +83 kernel/bpf/inode.c
81
82 /* Handler for any inode event. */
> 83 int handle_inode_event(struct fsnotify_mark *mark, u32 mask,
84 struct inode *inode, struct inode *dir,
85 const struct qstr *file_name, u32 cookie)
86 {
87 return 0;
88 }
89
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2022-01-07 0:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 21:50 [PATCH RFC bpf-next v1 0/8] Pinning bpf objects outside bpffs Hao Luo
2022-01-06 21:50 ` [PATCH RFC bpf-next v1 1/8] bpf: Support pinning in non-bpf file system Hao Luo
2022-01-07 0:04 ` kernel test robot [this message]
2022-01-07 0:33 ` Yonghong Song
2022-01-08 0:41 ` kernel test robot
2022-01-08 0:41 ` kernel test robot
2022-01-06 21:50 ` [PATCH RFC bpf-next v1 2/8] bpf: Record back pointer to the inode in bpffs Hao Luo
2022-01-06 21:50 ` [PATCH RFC bpf-next v1 3/8] bpf: Expose bpf object in kernfs Hao Luo
2022-01-06 21:50 ` [PATCH RFC bpf-next v1 4/8] bpf: Support removing kernfs entries Hao Luo
2022-01-06 21:50 ` [PATCH RFC bpf-next v1 5/8] bpf: Introduce a new program type bpf_view Hao Luo
2022-01-07 0:35 ` Yonghong Song
2022-01-06 21:50 ` [PATCH RFC bpf-next v1 6/8] libbpf: Support of bpf_view prog type Hao Luo
2022-01-06 21:50 ` [PATCH RFC bpf-next v1 7/8] bpf: Add seq_show operation for bpf in cgroupfs Hao Luo
2022-01-06 21:50 ` [PATCH RFC bpf-next v1 8/8] selftests/bpf: Test exposing bpf objects in kernfs Hao Luo
2022-01-06 23:02 ` [PATCH RFC bpf-next v1 0/8] Pinning bpf objects outside bpffs sdf
2022-01-07 18:59 ` Hao Luo
2022-01-07 19:25 ` sdf
2022-01-10 18:55 ` Hao Luo
2022-01-10 19:22 ` Stanislav Fomichev
2022-01-11 3:33 ` Alexei Starovoitov
2022-01-11 17:06 ` Stanislav Fomichev
2022-01-11 18:20 ` Hao Luo
2022-01-12 18:55 ` Song Liu
2022-01-12 19:19 ` Hao Luo
2022-01-07 0:30 ` Yonghong Song
2022-01-07 20:43 ` Hao Luo
2022-01-10 17:30 ` Yonghong Song
2022-01-10 18:56 ` Hao Luo
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=202201070824.fU5x5JHr-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.