From: Markus Metzger <markus.t.metzger@intel.com>
To: linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
hpa@zytor.com
Cc: markus.t.metzger@intel.com, markus.t.metzger@gmail.com,
roland@redhat.com, eranian@googlemail.com, oleg@redhat.com,
juan.villacis@intel.com, ak@linux.jf.intel.com
Subject: [patch 1/14] x86, ptrace: add arch_ptrace_report_exit
Date: Fri, 27 Mar 2009 09:46:26 +0100 [thread overview]
Message-ID: <20090327094626.A11002@sedona.ch.intel.com> (raw)
Add an arch_ variant to report a task exit.
Move the ptrace report exit code from tracehook.h to ptrace.h.
Signed-off-by: Markus Metzger <markus.t.metzger@intel.com>
---
Index: git-tip/include/linux/ptrace.h
===================================================================
--- git-tip.orig/include/linux/ptrace.h 2009-03-23 10:45:30.000000000 +0100
+++ git-tip/include/linux/ptrace.h 2009-03-23 11:31:21.000000000 +0100
@@ -335,6 +335,23 @@ static inline void user_enable_block_ste
#define arch_ptrace_fork(child, clone_flags) do { } while (0)
#endif
+#ifndef arch_ptrace_report_exit
+/**
+ * arch_ptrace_report_exit - Do machine specific work for exiting ptraced tasks
+ * @exit_code: current->exit_code value
+ *
+ * This is called early from do_exit() with no locks held after we notified the
+ * ptracer.
+ */
+#define arch_ptrace_report_exit(exit_code) do { } while (0)
+#endif
+
+static inline void ptrace_report_exit(long *exit_code)
+{
+ ptrace_event(PT_TRACE_EXIT, PTRACE_EVENT_EXIT, *exit_code);
+ arch_ptrace_report_exit(*exit_code);
+}
+
extern int task_current_syscall(struct task_struct *target, long *callno,
unsigned long args[6], unsigned int maxargs,
unsigned long *sp, unsigned long *pc);
Index: git-tip/include/linux/tracehook.h
===================================================================
--- git-tip.orig/include/linux/tracehook.h 2009-03-23 10:45:30.000000000 +0100
+++ git-tip/include/linux/tracehook.h 2009-03-23 11:31:21.000000000 +0100
@@ -211,7 +211,7 @@ static inline void tracehook_report_exec
*/
static inline void tracehook_report_exit(long *exit_code)
{
- ptrace_event(PT_TRACE_EXIT, PTRACE_EVENT_EXIT, *exit_code);
+ ptrace_report_exit(exit_code);
}
/**
---------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next reply other threads:[~2009-03-27 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 8:46 Markus Metzger [this message]
2009-03-27 14:19 ` [patch 1/14] x86, ptrace: add arch_ptrace_report_exit Oleg Nesterov
2009-03-27 15:12 ` Metzger, Markus T
2009-03-27 17:07 ` Oleg Nesterov
2009-03-27 17:37 ` Markus Metzger
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=20090327094626.A11002@sedona.ch.intel.com \
--to=markus.t.metzger@intel.com \
--cc=ak@linux.jf.intel.com \
--cc=eranian@googlemail.com \
--cc=hpa@zytor.com \
--cc=juan.villacis@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@gmail.com \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.