Hi Stanislav, Thank you for the patch! Yet something to improve:
[auto build test ERROR on bpf/master] [also build test ERROR on net/master net-next/master v5.8-rc2 next-20200625] [cannot apply to bpf-next/master] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/Stanislav-Fomichev/bpf-add-BPF_CGROUP_INET_SOCK_RELEASE-hook/20200626-081210 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master config: x86_64-defconfig (attached as .config) compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 6e11ed52057ffc39941cb2de6d93cae522db4782) 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 # install x86_64 cross compiling tool for clang build # apt-get install binutils-x86-64-linux-gnu # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <l...@intel.com> All errors (new ones prefixed by >>): >> net/ipv4/af_inet.c:415:4: error: implicit declaration of function >> 'BPF_CGROUP_RUN_PROG_INET_SOCK_RELEASE' >> [-Werror,-Wimplicit-function-declaration] BPF_CGROUP_RUN_PROG_INET_SOCK_RELEASE(sk); ^ 1 error generated. vim +/BPF_CGROUP_RUN_PROG_INET_SOCK_RELEASE +415 net/ipv4/af_inet.c 400 401 402 /* 403 * The peer socket should always be NULL (or else). When we call this 404 * function we are destroying the object and from then on nobody 405 * should refer to it. 406 */ 407 int inet_release(struct socket *sock) 408 { 409 struct sock *sk = sock->sk; 410 411 if (sk) { 412 long timeout; 413 414 if (!sk->sk_kern_sock) > 415 BPF_CGROUP_RUN_PROG_INET_SOCK_RELEASE(sk); 416 417 /* Applications forget to leave groups before exiting */ 418 ip_mc_drop_socket(sk); 419 420 /* If linger is set, we don't return until the close 421 * is complete. Otherwise we return immediately. The 422 * actually closing is done the same either way. 423 * 424 * If the close is due to the process exiting, we never 425 * linger.. 426 */ 427 timeout = 0; 428 if (sock_flag(sk, SOCK_LINGER) && 429 !(current->flags & PF_EXITING)) 430 timeout = sk->sk_lingertime; 431 sk->sk_prot->close(sk, timeout); 432 sock->sk = NULL; 433 } 434 return 0; 435 } 436 EXPORT_SYMBOL(inet_release); 437 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-...@lists.01.org
.config.gz
Description: application/gzip
