From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: bpf <bpf@vger.kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Hari Bathini <hbathini@linux.ibm.com>,
Saket Kumar Bhaskar <skb99@linux.ibm.com>
Subject: [mainline] selftests/bpf: struct_ops_assoc test hangs indefinitely on PowerPC
Date: Fri, 29 May 2026 19:22:29 +0530 [thread overview]
Message-ID: <d6cb7128-3cff-4a9f-ac9e-410009b2890e@linux.ibm.com> (raw)
Greetings!!!
The struct_ops_assoc/st_ops_assoc_in_timer selftest hangs indefinitely on
PowerPC, spinning in sched_yield() until watchdog timeout.
**Test Failure:**
./test_progs -t struct_ops_assoc
WATCHDOG: test case struct_ops_assoc/st_ops_assoc_in_timer executes for
10 seconds...
WATCHDOG: test case struct_ops_assoc/st_ops_assoc_in_timer executes for
120 seconds, terminating with SIGSEGV
#445 struct_ops_assoc:FAIL
**Architecture:** PowerPC 64-bit (ppc64le)
**Kernel:** 7.1.0-rc5-00149-g8fde5d1d47f6
**Symptoms:**
Test hangs indefinitely in infinite loop, repeatedly calling sched_yield():
Stack trace:
./test_progs(crash_handler+0x34)
linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)
/lib64/libc.so.6(__sched_yield+0x2c) ← stuck here
./test_progs() [0x105ae220]
./test_progs(test_struct_ops_assoc+0x88)
./test_progs(main+0x7ac)
If you happen to fix this, please add below tag.
Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Regards,
Venkat.
reply other threads:[~2026-05-29 13:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d6cb7128-3cff-4a9f-ac9e-410009b2890e@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hbathini@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=skb99@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox