All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Richter <tmricht@linux.ibm.com>
To: "linux-perf-use." <linux-perf-users@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@redhat.com>,
	Sumanth Korikkar <sumanthk@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	vasily Gorbik <gor@linux.ibm.com>,
	Ian Rogers <irogers@google.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>
Subject: perf test case 40 LLVM search and compile runs endless (eBPF linkage issue)
Date: Mon, 23 May 2022 12:52:06 +0200	[thread overview]
Message-ID: <bac4efca-c61e-5f62-daa1-f508b64d6a7f@linux.ibm.com> (raw)

On s390 the test case 40 'LLVM search and compile' runs for ever:

  # date; timeout 30s perf test -F 40; date
  Mon May 23 12:35:48 PM CEST 2022
   40: LLVM search and compile   :
   40.1: Basic BPF llvm compile  :
  Mon May 23 12:36:18 PM CEST 2022
  #

Investigation by Ilya Leoshkevich revealed:
On s390 we hit an endless loop where bpf_object__next_program and bpf_program__next 
infinitely call each other. We tracked this down to ld.so preferring the perf's 
bpf_object__next_program weak copy over the libbpf's strong one.

This is introduced with commit 2a4898fc264a ("perf tools: Add more weak libbpf functions")

Also see discussion in 
https://lore.kernel.org/lkml/YY%2FAR2Dcaws0BAE9@kernel.org/

How can this be fixed asap? Thanks a lot.
-- 
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
Vorsitzender des Aufsichtsrats: Gregor Pillen
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294

             reply	other threads:[~2022-05-23 10:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 10:52 Thomas Richter [this message]
2022-05-23 11:09 ` perf test case 40 LLVM search and compile runs endless (eBPF linkage issue) Jiri Olsa
2022-05-24 12:10   ` Jiri Olsa
2022-05-24 14:33     ` Arnaldo Carvalho de Melo
2022-05-25 14:10       ` Thomas Richter

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=bac4efca-c61e-5f62-daa1-f508b64d6a7f@linux.ibm.com \
    --to=tmricht@linux.ibm.com \
    --cc=acme@kernel.org \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sumanthk@linux.ibm.com \
    --cc=svens@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 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.