From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: vapier@gentoo.org, linux-parisc@vger.kernel.org,
roland@redhat.com, "David S. Miller" <davem@davemloft.net>,
Paul Mundt <lethal@linux-sh.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] parisc: fix tracing of signals
Date: Fri, 12 Feb 2010 08:21:33 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1002120816100.7792@localhost.localdomain> (raw)
In-Reply-To: <20100212155306.GI24051@bombadil.infradead.org>
On Fri, 12 Feb 2010, Kyle McMartin wrote:
>
> Mike Frysinger pointed out that calling tracehook_signal_handler with
> stepping=0 missed testing the thread flags, resulting in not calling
> ptrace_notify. Fix this by testing if we're single stepping or branch
> stepping and setting the flag accordingly.
>
> Tested, seems to work.
Hmm. All other architectures either pass in zero, or test TIF_SINGLESTEP.
I guess TIF_BLOCKSTEP is a parisc addition, so now parisc matches x86 and
power etc, but it still makes me wonder about all those other
architectures that pass in zero.
For the curious, that seems to be at least sparc and 64-bit (but not
32-bit) sh.
David? Paul?
Linus
---
> Reported-by: Mike Frysinger <vapier@gentoo.org>
> Signed-off-by: Kyle McMartin <kyle@mcmartin.ca>
> ---
> arch/parisc/kernel/signal.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/arch/parisc/kernel/signal.c b/arch/parisc/kernel/signal.c
> index e8467e4..07b3dac 100644
> --- a/arch/parisc/kernel/signal.c
> +++ b/arch/parisc/kernel/signal.c
> @@ -469,7 +469,9 @@ handle_signal(unsigned long sig, siginfo_t *info, struct k_sigaction *ka,
> recalc_sigpending();
> spin_unlock_irq(¤t->sighand->siglock);
>
> - tracehook_signal_handler(sig, info, ka, regs, 0);
> + tracehook_signal_handler(sig, info, ka, regs,
> + test_thread_flag(TIF_SINGLESTEP) ||
> + test_thread_flag(TIF_BLOCKSTEP));
>
> return 1;
> }
> --
> 1.6.6
>
next prev parent reply other threads:[~2010-02-12 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 15:53 [PATCH] parisc: fix tracing of signals Kyle McMartin
2010-02-12 16:21 ` Linus Torvalds [this message]
2010-02-12 17:10 ` Kyle McMartin
2010-02-12 23:58 ` Mike Frysinger
2010-02-13 11:03 ` Paul Mundt
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=alpine.LFD.2.00.1002120816100.7792@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kyle@mcmartin.ca \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=roland@redhat.com \
--cc=vapier@gentoo.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