netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: YangYuxi <yx.atom1@gmail.com>,
	ast@kernel.org, daniel@iogearbox.net, kafai@fb.com,
	songliubraving@fb.com, yhs@fb.com, andriin@fb.com,
	john.fastabend@gmail.com, kpsingh@chromium.org,
	netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com
Subject: Re: [PATCH] ebpf: fix parameter naming confusing
Date: Fri, 17 Jul 2020 01:49:54 +0800	[thread overview]
Message-ID: <202007170137.pGaM7wZf%lkp@intel.com> (raw)
In-Reply-To: <20200716134154.GA7123@vm_111_229_centos>

[-- Attachment #1: Type: text/plain, Size: 2788 bytes --]

Hi YangYuxi,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on bpf-next/master]
[also build test ERROR on bpf/master net/master ipvs/master net-next/master v5.8-rc5 next-20200716]
[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]

url:    https://github.com/0day-ci/linux/commits/YangYuxi/ebpf-fix-parameter-naming-confusing/20200716-214501
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: powerpc64-randconfig-r003-20200716 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project ed6b578040a85977026c93bf4188f996148f3218)
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 powerpc64 cross compiling tool for clang build
        # apt-get install binutils-powerpc64-linux-gnu
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=powerpc64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> kernel/bpf/syscall.c:1887:7: error: use of undeclared identifier 'attach_type'
           if (!attach_type)
                ^
   1 error generated.

vim +/attach_type +1887 kernel/bpf/syscall.c

b16d9aa4c2b90a Martin KaFai Lau 2017-06-05  1882  
040ee69226f8a9 Al Viro          2017-12-02  1883  bool bpf_prog_get_ok(struct bpf_prog *prog,
10eb063762081a YangYuxi         2020-07-16  1884  			    enum bpf_prog_type *prog_type, bool attach_drv)
248f346ffe9508 Jakub Kicinski   2017-11-03  1885  {
288b3de55aace8 Jakub Kicinski   2017-11-20  1886  	/* not an attachment, just a refcount inc, always allow */
288b3de55aace8 Jakub Kicinski   2017-11-20 @1887  	if (!attach_type)
288b3de55aace8 Jakub Kicinski   2017-11-20  1888  		return true;
248f346ffe9508 Jakub Kicinski   2017-11-03  1889  
10eb063762081a YangYuxi         2020-07-16  1890  	if (prog->type != *prog_type)
248f346ffe9508 Jakub Kicinski   2017-11-03  1891  		return false;
288b3de55aace8 Jakub Kicinski   2017-11-20  1892  	if (bpf_prog_is_dev_bound(prog->aux) && !attach_drv)
248f346ffe9508 Jakub Kicinski   2017-11-03  1893  		return false;
248f346ffe9508 Jakub Kicinski   2017-11-03  1894  
248f346ffe9508 Jakub Kicinski   2017-11-03  1895  	return true;
248f346ffe9508 Jakub Kicinski   2017-11-03  1896  }
248f346ffe9508 Jakub Kicinski   2017-11-03  1897  

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28194 bytes --]

  parent reply	other threads:[~2020-07-16 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 13:41 [PATCH] ebpf: fix parameter naming confusing YangYuxi
2020-07-16 15:18 ` kernel test robot
2020-07-16 17:49 ` kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-17  2:08 YangYuxi
2020-07-21 19:17 ` Alexei Starovoitov

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=202007170137.pGaM7wZf%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andriin@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kpsingh@chromium.org \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.com \
    --cc=yx.atom1@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).