From: Josh Hunt <johunt@akamai.com>
To: john@metanate.com, jolsa@kernel.org,
alexander.shishkin@linux.intel.com, khlebnikov@yandex-team.ru,
namhyung@kernel.org, peterz@infradead.org, acme@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: 4.19 dwarf unwinding broken
Date: Thu, 3 Oct 2019 00:54:09 -0700 [thread overview]
Message-ID: <ab87d20b-526c-9435-0532-c298beeb0318@akamai.com> (raw)
The following commit is breaking dwarf unwinding on 4.19 kernels:
commit e5adfc3e7e774ba86f7bb725c6eef5f32df8630e
Author: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Date: Tue Aug 7 12:09:01 2018 +0300
perf map: Synthesize maps only for thread group leader
It looks like this was fixed later by:
commit e8ba2906f6b9054102ad035ac9cafad9d4168589
Author: John Keeping <john@metanate.com>
Date: Thu Aug 15 11:01:45 2019 +0100
perf unwind: Fix libunwind when tid != pid
but was not selected as a backport to 4.19. Are there plans to backport
the fix? If not, could we have the breaking commit reverted in 4.19 LTS?
Thanks
Josh
next reply other threads:[~2019-10-03 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 7:54 Josh Hunt [this message]
2019-10-03 10:03 ` 4.19 dwarf unwinding broken Jiri Olsa
2019-10-03 15:17 ` Josh Hunt
2019-10-03 16:04 ` Arnaldo Carvalho de Melo
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=ab87d20b-526c-9435-0532-c298beeb0318@akamai.com \
--to=johunt@akamai.com \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=john@metanate.com \
--cc=jolsa@kernel.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).