From: Tom Rini <trini@kernel.crashing.org>
To: discuss@x86-64.org,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
ak@suse.de
Subject: [PATCH 2.6.10-rc2] x86_64: only single-step into signal handlers if the tracer asked for it
Date: Thu, 18 Nov 2004 08:42:19 -0700 [thread overview]
Message-ID: <20041118154219.GJ4583@smtp.west.cox.net> (raw)
In-Reply-To: <200411150203.iAF23Trb024677@hera.kernel.org>
On Mon, Nov 15, 2004 at 08:56:31AM +0000, torvalds@ppc970.osdl.org wrote:
> ChangeSet 1.2159, 2004/11/15 00:56:31-08:00, torvalds@ppc970.osdl.org
>
> x86: only single-step into signal handlers if the tracer
> asked for it.
x86_64 looks to have the same issue. But I deferr to the experts (and
hope this isn't a dupe).
Signed-off-by: Tom Rini <trini@kernel.crashing.org>
--- 1.28/arch/x86_64/kernel/signal.c 2004-09-08 11:52:55 -07:00
+++ edited/arch/x86_64/kernel/signal.c 2004-11-18 08:27:59 -07:00
@@ -325,7 +325,7 @@
set_fs(USER_DS);
if (regs->eflags & TF_MASK) {
- if (current->ptrace & PT_PTRACED) {
+ if ((current->ptrace & (PT_PTRACED | PT_DTRACE)) == (PT_PTRACED | PT_DTRACE)) {
ptrace_notify(SIGTRAP);
} else {
regs->eflags &= ~TF_MASK;
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-11-18 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200411150203.iAF23Trb024677@hera.kernel.org>
2004-11-15 2:20 ` x86: only single-step into signal handlers if the tracer Jeff Garzik
2004-11-15 2:44 ` Andrew Morton
2004-11-15 12:10 ` Alexander Nyberg
2004-11-18 15:42 ` Tom Rini [this message]
2004-11-18 20:46 ` [discuss] [PATCH 2.6.10-rc2] x86_64: only single-step into signal handlers if the tracer asked for it Andi Kleen
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=20041118154219.GJ4583@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--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