From: kernel test robot <lkp@intel.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [kkdwivedi:cancellations 17/40] fdesc.c:undefined reference to `bpf_sk_release_proto'
Date: Wed, 21 Oct 2026 10:10:02 +0800 [thread overview]
Message-ID: <202610210917.nPIPoGWv-lkp@intel.com> (raw)
tree: https://github.com/kkdwivedi/linux cancellations
head: d3a43c8a05ca2e56ecb592c265a238386f3f1ff3
commit: d5b5e8f94c6af8caf3e43d13671a6bf25dee3759 [17/40] bpf: Release frame descriptor resources from bpf_throw_unwind()
config: loongarch-randconfig-1000-20261021 (https://download.01.org/0day-ci/archive/20261021/202610210917.nPIPoGWv-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261021/202610210917.nPIPoGWv-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/202610210917.nPIPoGWv-lkp@intel.com/
All errors (new ones prefixed by >>):
loongarch64-linux-ld: kernel/bpf/fdesc.o: in function `.L166':
>> fdesc.c:(.text+0xe80): undefined reference to `bpf_sk_release_proto'
>> loongarch64-linux-ld: fdesc.c:(.text+0xe84): undefined reference to `bpf_sk_release_proto'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-10-21 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 2:10 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-20 8:53 [kkdwivedi:cancellations 17/40] fdesc.c:undefined reference to `bpf_sk_release_proto' 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=202610210917.nPIPoGWv-lkp@intel.com \
--to=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 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.