From: Song Liu <song@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [linux-next:master 3585/10295] WARN: resolve_btfids: unresolved symbol bpf_get_file_xattr
Date: Sun, 24 Dec 2023 16:50:43 -0800 [thread overview]
Message-ID: <CAPhsuW4_esoAtHWrikykR0bEc0SxK8n7u2BLoUkoN016R3x3LQ@mail.gmail.com> (raw)
In-Reply-To: <202312241609.w1nPmrz3-lkp@intel.com>
On Sun, Dec 24, 2023 at 1:03 AM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 39676dfe52331dba909c617f213fdb21015c8d10
> commit: ac9c05e0e453cfcab2866f6d28f257590e4f66e5 [3585/10295] bpf: Add kfunc bpf_get_file_xattr
> config: powerpc64-randconfig-r024-20220211 (https://download.01.org/0day-ci/archive/20231224/202312241609.w1nPmrz3-lkp@intel.com/config)
> compiler: powerpc64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231224/202312241609.w1nPmrz3-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/202312241609.w1nPmrz3-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> WARN: resolve_btfids: unresolved symbol unix_sock
> WARN: resolve_btfids: unresolved symbol bpf_cpumask
> WARN: resolve_btfids: unresolved symbol bpf_verify_pkcs7_signature
> WARN: resolve_btfids: unresolved symbol bpf_lookup_user_key
> WARN: resolve_btfids: unresolved symbol bpf_lookup_system_key
> WARN: resolve_btfids: unresolved symbol bpf_key_put
> >> WARN: resolve_btfids: unresolved symbol bpf_get_file_xattr
We have one of these warnings for each BPF kfunc (for this config), so I
think this is expected.
Thanks,
Song
prev parent reply other threads:[~2023-12-25 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-24 9:01 kernel test robot
2023-12-25 0:50 ` Song Liu [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=CAPhsuW4_esoAtHWrikykR0bEc0SxK8n7u2BLoUkoN016R3x3LQ@mail.gmail.com \
--to=song@kernel.org \
--cc=ast@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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