From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, linux-security-module@wirex.com
Subject: Re: [BK PATCH] LSM changes for 2.5.27
Date: Mon, 22 Jul 2002 17:40:34 -0700 [thread overview]
Message-ID: <20020723004034.GG660@kroah.com> (raw)
In-Reply-To: <20020723004007.GF660@kroah.com>
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.683.1.4 -> 1.683.1.5
# arch/ia64/kernel/ptrace.c 1.10 -> 1.11
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 02/07/22 greg@kroah.com 1.683.1.5
# added ptrace hook for ia64
# --------------------------------------------
#
diff -Nru a/arch/ia64/kernel/ptrace.c b/arch/ia64/kernel/ptrace.c
--- a/arch/ia64/kernel/ptrace.c Mon Jul 22 17:25:56 2002
+++ b/arch/ia64/kernel/ptrace.c Mon Jul 22 17:25:56 2002
@@ -15,6 +15,7 @@
#include <linux/ptrace.h>
#include <linux/smp_lock.h>
#include <linux/user.h>
+#include <linux/security.h>
#include <asm/pgtable.h>
#include <asm/processor.h>
@@ -1099,6 +1100,9 @@
if (request == PTRACE_TRACEME) {
/* are we already being traced? */
if (current->ptrace & PT_PTRACED)
+ goto out;
+ ret = security_ops->ptrace(current->parent, current);
+ if (ret)
goto out;
current->ptrace |= PT_PTRACED;
ret = 0;
next prev parent reply other threads:[~2002-07-23 0:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 0:37 [BK PATCH] LSM changes for 2.5.27 Greg KH
2002-07-23 0:38 ` Greg KH
2002-07-23 0:39 ` Greg KH
2002-07-23 0:39 ` Greg KH
2002-07-23 0:39 ` Greg KH
2002-07-23 0:40 ` Greg KH
2002-07-23 0:40 ` Greg KH [this message]
2002-07-23 0:40 ` Greg KH
2002-07-23 0:43 ` Greg KH
2002-07-23 0:44 ` Greg KH
2002-07-23 8:16 ` Roman Zippel
2002-07-23 13:16 ` Alan Cox
2002-07-24 19:56 ` Greg KH
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=20020723004034.GG660@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.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