All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Rantala, Tommi T. (Nokia - FI/Espoo)" <tommi.t.rantala@nokia.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jan.kratochvil@redhat.com" <jan.kratochvil@redhat.com>
Subject: Re: LTS perf unwind fix
Date: Thu, 27 May 2021 12:22:37 +0200	[thread overview]
Message-ID: <YK9y7dd+wsp2OLD/@kroah.com> (raw)
In-Reply-To: <ef44cde0f3493eb9ab2efe951bc03e4e6ccc416b.camel@nokia.com>

On Thu, May 27, 2021 at 10:04:51AM +0000, Rantala, Tommi T. (Nokia - FI/Espoo) wrote:
> Hi Greg,
> 
> Please apply these two commits to 5.4.y
> (other LTSes are probably fine too, but I didn't test):
> 
> 
> commit bf53fc6b5f415cddc7118091cb8fd6a211b2320d
> Author: Jan Kratochvil <jan.kratochvil@redhat.com>
> Date:   Fri Dec 4 09:17:02 2020 -0300
> 
>     perf unwind: Fix separate debug info files when using elfutils'
> libdw's unwinder
> 
> 
> commit 4e1481445407b86a483616c4542ffdc810efb680
> Author: Dave Rigby <d.rigby@me.com>
> Date:   Thu Feb 18 16:56:54 2021 +0000
> 
>     perf unwind: Set userdata for all __report_module() paths
> 
>     [...]
> 
>     Fixes: bf53fc6b5f41 ("perf unwind: Fix separate debug info files
> when using elfutils' libdw's unwinder")
> 
> 
> These commits fix some broken backtraces when using the perf tool.

Also queued up for the 5.10.y tree as you do not want to move to a newer
kernel and have a regression.

thanks,

greg k-h

      reply	other threads:[~2021-05-27 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 12:41 LTS perf unwind fix Rantala, Tommi T. (Nokia - FI/Espoo)
2021-05-25 12:47 ` Jan Kratochvil
2021-05-25 13:06 ` gregkh
2021-05-26  7:21   ` Rantala, Tommi T. (Nokia - FI/Espoo)
2021-05-27  9:16     ` gregkh
2021-05-27 10:04       ` Rantala, Tommi T. (Nokia - FI/Espoo)
2021-05-27 10:22         ` gregkh [this message]

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=YK9y7dd+wsp2OLD/@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tommi.t.rantala@nokia.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.