From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Kumar Kartikeya Dwivedi <memxor@gmail.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [linux-next:master 5430/5912] kernel/bpf/verifier.c:15232:13: warning: variable 'prev_offset' set but not used
Date: Tue, 19 Sep 2023 02:33:19 -0700 [thread overview]
Message-ID: <CAADnVQLvqidYQp4jnrL+ryi5o32P-yqHgrQ+aKdp5gvDBndbJw@mail.gmail.com> (raw)
In-Reply-To: <202309190634.fL17FWoT-lkp@intel.com>
On Mon, Sep 18, 2023 at 3:31 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 7fc7222d9680366edeecc219c21ca96310bdbc10
> commit: aaa619ebccb2b78b3c6d2c0cd72d206ee8fc0025 [5430/5912] bpf: Refactor check_btf_func and split into two phases
> config: arc-randconfig-002-20230919 (https://download.01.org/0day-ci/archive/20230919/202309190634.fL17FWoT-lkp@intel.com/config)
> compiler: arc-elf-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230919/202309190634.fL17FWoT-lkp@intel.com/reproduce)
>
> 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: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202309190634.fL17FWoT-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> kernel/bpf/verifier.c: In function 'check_btf_func':
> >> kernel/bpf/verifier.c:15232:13: warning: variable 'prev_offset' set but not used [-Wunused-but-set-variable]
> 15232 | u32 prev_offset = 0;
> | ^~~~~~~~~~~
> >> kernel/bpf/verifier.c:15225:35: warning: variable 'min_size' set but not used [-Wunused-but-set-variable]
> 15225 | u32 i, nfuncs, urec_size, min_size;
> | ^~~~~~~~
Applied trivial fix to bpf-next.
prev parent reply other threads:[~2023-09-19 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 22:30 kernel test robot
2023-09-19 9:33 ` Alexei Starovoitov [this message]
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=CAADnVQLvqidYQp4jnrL+ryi5o32P-yqHgrQ+aKdp5gvDBndbJw@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=memxor@gmail.com \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox