Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 3 Oct 2019 12:03:00 +0200
From:   Jiri Olsa <jolsa@redhat.com>
To:     Josh Hunt <johunt@akamai.com>
Cc:     john@metanate.com, jolsa@kernel.org,
        alexander.shishkin@linux.intel.com, khlebnikov@yandex-team.ru,
        namhyung@kernel.org, peterz@infradead.org, acme@redhat.com,
        linux-kernel@vger.kernel.org
Subject: Re: 4.19 dwarf unwinding broken
Message-ID: <20191003100300.GA22784@krava>
References: <ab87d20b-526c-9435-0532-c298beeb0318@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ab87d20b-526c-9435-0532-c298beeb0318@akamai.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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@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