From: Anton Protopopov <aspsk@isovalent.com>
To: Yujie Liu <yujie.liu@intel.com>
Cc: kernel test robot <lkp@intel.com>,
bpf@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
Joe Stringer <joe@isovalent.com>,
John Fastabend <john.fastabend@gmail.com>
Subject: Re: [PATCH bpf-next 1/2] bpf: add new map ops ->map_pressure
Date: Tue, 13 Jun 2023 08:30:23 +0000 [thread overview]
Message-ID: <ZIgpH43cHO9ZEz73@zh-lab-node-5> (raw)
In-Reply-To: <ZIgngQXrlaCtAYgl@yujie-X299>
On Tue, Jun 13, 2023 at 04:23:29PM +0800, Yujie Liu wrote:
> Hi Anton,
>
> Sorry for the late reply.
>
> On Thu, Jun 01, 2023 at 07:50:00AM +0000, Anton Protopopov wrote:
> > On Thu, Jun 01, 2023 at 08:44:24AM +0800, kernel test robot wrote:
> > > Hi Anton,
> > >
> > > kernel test robot noticed the following build errors:
> > >
> > > [...]
> > >
> > > If you fix the issue, kindly add following tag where applicable
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202306010837.mGhA199K-lkp@intel.com/
> >
> > How does this apply to patches? If I send a v2, should I include these tags
> > there?
>
> If a v2 is sent, these tags should not be included.
>
> > If this patch gets rejected, is there need to do anything to close the
> > robot's ticket?
>
> No need to close this ticket.
>
> Thanks for raising above concerns. We have updated the wording in our
> reports as below to avoid misinterpretation:
>
> 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: ...
> | Closes: ...
Great, thanks for the explanations!
> --
> Best Regards,
> Yujie
>
> > > All errors (new ones prefixed by >>):
> > >
> > > kernel/bpf/hashtab.c: In function 'htab_map_pressure':
> > > >> kernel/bpf/hashtab.c:189:24: error: implicit declaration of function '__percpu_counter_sum'; did you mean 'percpu_counter_sum'? [-Werror=implicit-function-declaration]
> > > 189 | return __percpu_counter_sum(&htab->pcount);
> > > | ^~~~~~~~~~~~~~~~~~~~
> > > | percpu_counter_sum
> > > cc1: some warnings being treated as errors
> > >
> > >
> > > vim +189 kernel/bpf/hashtab.c
> > >
> > > 183
> > > 184 static u32 htab_map_pressure(const struct bpf_map *map)
> > > 185 {
> > > 186 struct bpf_htab *htab = container_of(map, struct bpf_htab, map);
> > > 187
> > > 188 if (htab->use_percpu_counter)
> > > > 189 return __percpu_counter_sum(&htab->pcount);
> > > 190 return atomic_read(&htab->count);
> > > 191 }
> > > 192
> >
> > (This bug happens for !SMP case.)
> >
> > > --
> > > 0-DAY CI Kernel Test Service
> > > https://github.com/intel/lkp-tests/wiki
> >
next prev parent reply other threads:[~2023-06-13 8:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 11:05 [PATCH bpf-next 0/2] add mechanism to report map pressure Anton Protopopov
2023-05-31 11:05 ` [PATCH bpf-next 1/2] bpf: add new map ops ->map_pressure Anton Protopopov
2023-05-31 18:24 ` Alexei Starovoitov
2023-06-01 7:31 ` Anton Protopopov
2023-06-01 16:39 ` Alexei Starovoitov
2023-06-01 18:18 ` Anton Protopopov
2023-06-01 18:24 ` Alexei Starovoitov
2023-06-02 0:40 ` Alexei Starovoitov
2023-06-02 14:21 ` Anton Protopopov
2023-06-02 16:23 ` Alexei Starovoitov
2023-06-06 7:49 ` Anton Protopopov
2023-06-24 0:00 ` John Fastabend
2023-06-26 16:29 ` Anton Protopopov
2023-06-28 13:17 ` Anton Protopopov
2023-06-01 0:44 ` kernel test robot
2023-06-01 7:50 ` Anton Protopopov
2023-06-13 8:23 ` Yujie Liu
2023-06-13 8:30 ` Anton Protopopov [this message]
2023-05-31 11:05 ` [PATCH bpf-next 2/2] selftests/bpf: test map pressure Anton Protopopov
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=ZIgpH43cHO9ZEz73@zh-lab-node-5 \
--to=aspsk@isovalent.com \
--cc=bpf@vger.kernel.org \
--cc=joe@isovalent.com \
--cc=john.fastabend@gmail.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yujie.liu@intel.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 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.