From: Arun Sharma <asharma@fb.com>
To: linux-kernel@vger.kernel.org
Cc: Arun Sharma <asharma@fb.com>
Subject: [PATCH 0/3] perf: Support multiple stacks (v2)
Date: Fri, 20 Apr 2012 12:35:24 -0700 [thread overview]
Message-ID: <1334950527-5050-1-git-send-email-asharma@fb.com> (raw)
If userspace has two or more stacks and we happen to take a sample when
the stack pointer is pointing to a higher stack, we might get truncated
callchains. This patch series tries to address that.
Changelog:
v2: do this for compat32 as well
v2: improve safety checks and reduce max callchain size
Arun Sharma (3):
perf, x86: Allow multiple stacks
perf, x86: Don't leak kernel data via callchains
perf, x86: Limit callchains to 127
arch/x86/kernel/cpu/perf_event.c | 14 +++++++-------
include/linux/perf_event.h | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
--
1.7.8.4
next reply other threads:[~2012-04-20 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 19:35 Arun Sharma [this message]
2012-04-20 19:35 ` [PATCH 1/3] perf, x86: Allow multiple stacks Arun Sharma
2012-04-20 19:35 ` [PATCH 2/3] perf, x86: Don't leak kernel data via callchains Arun Sharma
2012-04-20 19:57 ` Linus Torvalds
2012-04-20 19:35 ` [PATCH 3/3] perf: Limit callchains to 127 Arun Sharma
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=1334950527-5050-1-git-send-email-asharma@fb.com \
--to=asharma@fb.com \
--cc=linux-kernel@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®