mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Catalin Marinas <Catalin.Marinas@arm.com>
To: Olof Johansson <olof@lixom.net>
Cc: Will Deacon <Will.Deacon@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] ARM64: unwind: Fix PC calculation
Date: Sat, 15 Feb 2014 10:28:15 +0000	[thread overview]
Message-ID: <BBC3AB9B-17A9-4112-B8CC-D3DCB3B673D9@arm.com> (raw)
In-Reply-To: <1392406515-27835-1-git-send-email-olof@lixom.net>

On 14 Feb 2014, at 19:35, Olof Johansson <olof@lixom.net> wrote:
> The frame PC value in the unwind code used to just take the saved LR
> value and use that.  That's incorrect as a stack trace, since it shows
> the return path stack, not the call path stack.
>
> In particular, it shows faulty information in case the bl is done as
> the very last instruction of one label, since the return point will be
> in the next label. That can easily be seen with tail calls to panic(),
> which is marked __noreturn and thus doesn't have anything useful after it.
>
> Easiest here is to just correct the unwind code and do a -4, to get the
> actual call site for the backtrace instead of the return site.
>
> Signed-off-by: Olof Johansson <olof@lixom.net>
> Cc: stable@vger.kernel.org

Looks fine. I’ll push it sometime next week. Thanks.

Catalin

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No:  2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No:  2548782


  reply	other threads:[~2014-02-15 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 19:35 Olof Johansson
2014-02-15 10:28 ` Catalin Marinas [this message]
2014-02-15 10:41   ` Catalin Marinas

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=BBC3AB9B-17A9-4112-B8CC-D3DCB3B673D9@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=stable@vger.kernel.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

all inboxes | Powered by JetHome®