From: olofj@chromium.org (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Fix infinite loop in ARM user perf_event backtrace code
Date: Mon, 18 Apr 2011 11:31:09 -0700 [thread overview]
Message-ID: <BANLkTikwJzOXJGM4pcKmxVdP_2yb9uyeag@mail.gmail.com> (raw)
In-Reply-To: <1302924445-18557-1-git-send-email-sonnyrao@chromium.org>
On Fri, Apr 15, 2011 at 8:27 PM, Sonny Rao <sonnyrao@chromium.org> wrote:
>
> The ARM user backtrace code can get into an infinite loop if it
> runs into an invalid stack frame which points back to itself.
> This situation has been observed in practice. ?Fix it by capping
> the number of entries in the backtrace. ?This is also what other
> architectures do in their backtrace code.
>
> Signed-off-by: Sonny Rao <sonnyrao@chromium.org>
Acked-by: Olof Johansson <olof@lixom.net>
-Olof
prev parent reply other threads:[~2011-04-18 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 3:27 [PATCH] Fix infinite loop in ARM user perf_event backtrace code Sonny Rao
2011-04-18 10:42 ` Jamie Iles
2011-04-18 17:42 ` Will Deacon
2011-04-18 21:02 ` Sonny Rao
2011-04-18 18:31 ` Olof Johansson [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=BANLkTikwJzOXJGM4pcKmxVdP_2yb9uyeag@mail.gmail.com \
--to=olofj@chromium.org \
--cc=linux-arm-kernel@lists.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).