public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: dhowells@redhat.com, yasutake.koichi@jp.panasonic.com,
	linux-kernel@vger.kernel.org
Subject: arch/ && tracehook_report_syscall_xxx()
Date: Mon, 27 Apr 2009 20:04:55 +0200	[thread overview]
Message-ID: <20090427180455.GA32509@redhat.com> (raw)

We have a lot of code like arch/alpha/kernel/ptrace.c:syscall_trace()
in arch/ and I can't see how to convert them to use tracehooks.

The first problem, we don't know which hook should be called, there is
no entry/exit argument.

Still, I think it is better to change this code right now, and call
ptrace_report_syscall() directly.

But, the second problem, there is no "struct pt_regs *". What do you
think about the patch below?

However. I can't imagine how ptrace_report_syscall(regs) can actually
use "regs". Perhaps we can remove this argument?

Or what else do you think?

Hmm... and I can't understand how to change
arch/mn10300/kernel/ptrace.c:do_syscall_trace(), it does something
strange with TIF_SINGLESTEP. (maintainers cc'ed).

Oleg.

--- PTRACE/arch/alpha/kernel/ptrace.c~1_alpha	2009-04-06 00:03:35.000000000 +0200
+++ PTRACE/arch/alpha/kernel/ptrace.c	2009-04-27 19:11:50.000000000 +0200
@@ -11,6 +11,7 @@
 #include <linux/smp_lock.h>
 #include <linux/errno.h>
 #include <linux/ptrace.h>
+#include <linux/tracehook.h>
 #include <linux/user.h>
 #include <linux/slab.h>
 #include <linux/security.h>
@@ -354,20 +355,6 @@ syscall_trace(void)
 {
 	if (!test_thread_flag(TIF_SYSCALL_TRACE))
 		return;
-	if (!(current->ptrace & PT_PTRACED))
-		return;
-	/* The 0x80 provides a way for the tracing parent to distinguish
-	   between a syscall stop and SIGTRAP delivery */
-	ptrace_notify(SIGTRAP | ((current->ptrace & PT_TRACESYSGOOD)
-				 ? 0x80 : 0));
 
-	/*
-	 * This isn't the same as continuing with a signal, but it will do
-	 * for normal use.  strace only continues with a signal if the
-	 * stopping signal is not SIGTRAP.  -brl
-	 */
-	if (current->exit_code) {
-		send_sig(current->exit_code, current, 1);
-		current->exit_code = 0;
-	}
+	ptrace_report_syscall(NULL);
 }


             reply	other threads:[~2009-04-27 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 18:04 Oleg Nesterov [this message]
2009-04-27 18:29 ` arch/ && tracehook_report_syscall_xxx() Roland McGrath
2009-04-27 18:32   ` Christoph Hellwig
2009-04-29 19:08     ` Fwd: " Oleg Nesterov
2009-04-29 19:17       ` Roland McGrath
2009-04-29 19:30       ` Ingo Molnar
2009-04-29 19:44       ` Christoph Hellwig
2009-04-29 19:53       ` Kyle McMartin
2009-04-27 18:43   ` Oleg Nesterov
2009-04-27 19:24 ` David Howells

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=20090427180455.GA32509@redhat.com \
    --to=oleg@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=yasutake.koichi@jp.panasonic.com \
    /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