All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [kkdwivedi:cancellations 22/48] kernel/bpf/unwind.c:127:undefined reference to `bpf_sk_release_proto'
Date: Mon, 09 Nov 2026 15:24:48 +0100	[thread overview]
Message-ID: <202611091555.kZ1v3R4J-lkp@intel.com> (raw)

tree:   https://github.com/kkdwivedi/linux cancellations
head:   c5378a88f114558f34a5251ecc2e401d1c111548
commit: 2fd707f27a3e03d4bb53e381f93322a8a3f82919 [22/48] bpf: Add frame descriptor tables and release what they list when unwinding
config: s390-randconfig-2000-20261109 (https://download.01.org/0day-ci/archive/20261109/202611091555.kZ1v3R4J-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 14.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261109/202611091555.kZ1v3R4J-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/202611091555.kZ1v3R4J-lkp@intel.com/

All errors (new ones prefixed by >>):

   s390-linux-ld: kernel/bpf/unwind.o: in function `bpf_unwind_release':
>> kernel/bpf/unwind.c:127:(.text+0x9d8): undefined reference to `bpf_sk_release_proto'


vim +127 kernel/bpf/unwind.c

   102	
   103	/*
   104	 * Release one resource by its handle, at run time: the pointer to an object,
   105	 * the address of a stack object or of a lock, or nothing for a section.
   106	 * @flags is the saved IRQ flags of an irqsave lock. Not inlined so that every
   107	 * release of an unwind can be observed by attaching to this function.
   108	 */
   109	noinline void bpf_unwind_release(const struct bpf_resource *res, void *handle, void *flags)
   110	{
   111		/* A destructor that needs RCU protection gets it here, whatever the frames held. */
   112		if (res->rcu)
   113			rcu_read_lock();
   114		switch (res->kind) {
   115		case BPF_RESOURCE_OBJ:
   116			bpf_obj_drop_impl(handle, res->meta);
   117			break;
   118		case BPF_RESOURCE_PERCPU_OBJ:
   119			bpf_percpu_obj_drop_impl(handle, res->meta);
   120			break;
   121		case BPF_RESOURCE_KPTR:
   122		case BPF_RESOURCE_ITER:
   123			res->dtor(handle);
   124			break;
   125	#ifdef CONFIG_NET
   126		case BPF_RESOURCE_SOCK:
 > 127			bpf_sk_release_proto.func((u64)(long)handle, 0, 0, 0, 0);
   128			break;
   129	#endif
   130		case BPF_RESOURCE_RINGBUF:
   131			bpf_ringbuf_discard_proto.func((u64)(long)handle, 0, 0, 0, 0);
   132			break;
   133		case BPF_RESOURCE_DYNPTR_RINGBUF:
   134			bpf_ringbuf_discard_dynptr_proto.func((u64)(long)handle, 0, 0, 0, 0);
   135			break;
   136		case BPF_RESOURCE_SPIN_LOCK:
   137			bpf_spin_unlock_proto.func((u64)(long)handle, 0, 0, 0, 0);
   138			break;
   139		case BPF_RESOURCE_RES_LOCK:
   140			bpf_res_spin_unlock(handle);
   141			break;
   142		case BPF_RESOURCE_RES_LOCK_IRQ:
   143			bpf_res_spin_unlock_irqrestore(handle, flags);
   144			break;
   145		case BPF_RESOURCE_IRQ_FLAG:
   146			bpf_local_irq_restore(handle);
   147			break;
   148		case BPF_RESOURCE_IRQ_FLAG_LOCK:
   149			/* Restored together with the lock that saved them. */
   150			break;
   151		case BPF_RESOURCE_RCU:
   152			bpf_rcu_read_unlock();
   153			break;
   154		case BPF_RESOURCE_PREEMPT:
   155			bpf_preempt_enable();
   156			break;
   157		default:
   158			WARN_ON_ONCE(1);
   159		}
   160		if (res->rcu)
   161			rcu_read_unlock();
   162	}
   163	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2026-11-09 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 14:24 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-11-09 11:48 [kkdwivedi:cancellations 22/48] kernel/bpf/unwind.c:127: 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=202611091555.kZ1v3R4J-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.