lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191003100300.GA22784@krava>
Date:   Thu, 3 Oct 2019 12:03:00 +0200
From:   Jiri Olsa <jolsa@...hat.com>
To:     Josh Hunt <johunt@...mai.com>
Cc:     john@...anate.com, jolsa@...nel.org,
        alexander.shishkin@...ux.intel.com, khlebnikov@...dex-team.ru,
        namhyung@...nel.org, peterz@...radead.org, acme@...hat.com,
        linux-kernel@...r.kernel.org
Subject: Re: 4.19 dwarf unwinding broken

On Thu, Oct 03, 2019 at 12:54:09AM -0700, Josh Hunt wrote:
> The following commit is breaking dwarf unwinding on 4.19 kernels:

how?

jirka

> 
> commit e5adfc3e7e774ba86f7bb725c6eef5f32df8630e
> Author: Konstantin Khlebnikov <khlebnikov@...dex-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@...anate.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ