From: kernel test robot <lkp@intel.com>
To: Hou Tao <houtao1@huawei.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH bpf-next 1/3] bpf: Add support for qp-trie map
Date: Wed, 27 Jul 2022 04:20:04 +0800 [thread overview]
Message-ID: <202207270430.yGvLY2tk-lkp@intel.com> (raw)
In-Reply-To: <20220726130005.3102470-2-houtao1@huawei.com>
Hi Hou,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Hou-Tao/Add-support-for-qp-trie-map/20220726-204347
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: i386-randconfig-a002 (https://download.01.org/0day-ci/archive/20220727/202207270430.yGvLY2tk-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 83882606dbd7ffb0bdd3460356202d97705809c8)
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/intel-lab-lkp/linux/commit/74890023aaa2d8ffed54d96d4999f10bf14ccfef
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Hou-Tao/Add-support-for-qp-trie-map/20220726-204347
git checkout 74890023aaa2d8ffed54d96d4999f10bf14ccfef
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash kernel/bpf/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> kernel/bpf/bpf_qp_trie.c:622:24: warning: bitwise or with non-zero value always evaluates to true [-Wtautological-bitwise-compare]
if (!(attr->map_flags | BPF_F_NO_PREALLOC) ||
~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
1 warning generated.
vim +622 kernel/bpf/bpf_qp_trie.c
616
617 static int qp_trie_alloc_check(union bpf_attr *attr)
618 {
619 if (!bpf_capable())
620 return -EPERM;
621
> 622 if (!(attr->map_flags | BPF_F_NO_PREALLOC) ||
623 attr->map_flags & ~QP_TRIE_CREATE_FLAG_MASK ||
624 !bpf_map_flags_access_ok(attr->map_flags))
625 return -EINVAL;
626
627 if (!attr->max_entries || attr->key_size < QP_TRIE_MIN_KEY_SIZE ||
628 !attr->value_size)
629 return -EINVAL;
630
631 if (attr->key_size > QP_TRIE_MAX_KEY_SIZE ||
632 !is_valid_k_v_size(attr->key_size, attr->value_size))
633 return -E2BIG;
634
635 return 0;
636 }
637
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-07-26 20:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 13:00 [RFC PATCH bpf-next 0/3] Add support for qp-trie map Hou Tao
2022-07-26 13:00 ` [RFC PATCH bpf-next 1/3] bpf: " Hou Tao
2022-07-26 20:20 ` kernel test robot [this message]
2022-07-29 10:04 ` kernel test robot
2022-07-26 13:00 ` [RFC PATCH bpf-next 2/3] selftests/bpf: add a simple test for qp-trie Hou Tao
2022-07-26 13:00 ` [RFC PATCH bpf-next 3/3] selftests/bpf: add benchmark for qp-trie map Hou Tao
2022-08-02 6:20 ` [RFC PATCH bpf-next 0/3] Add support " Hou Tao
2022-08-02 22:38 ` Andrii Nakryiko
2022-08-08 17:54 ` Toke Høiland-Jørgensen
2022-08-09 8:25 ` houtao
2022-08-16 5:33 ` Andrii Nakryiko
-- strict thread matches above, loose matches on Subject: below --
2022-07-27 4:00 [RFC PATCH bpf-next 1/3] bpf: " kernel test robot
2022-08-02 16:56 kernel test robot
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=202207270430.yGvLY2tk-lkp@intel.com \
--to=lkp@intel.com \
--cc=houtao1@huawei.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@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.