From: joxeankoret@yahoo.es (Joxean Koret)
To: kernelnewbies@lists.kernelnewbies.org
Subject: cap_ptrace_access_check undefined
Date: Mon, 19 Mar 2012 11:06:05 +0100 [thread overview]
Message-ID: <1332151565.12845.89.camel@backup-server> (raw)
Hi all!
I'm writing a kernel module that needs to check if the current process
is attached (via ptrace) to some other process. So I do something like
this:
...
// verify pid
p = find_vpid(child_pid);
if ( p == NULL )
...
// get the task
task = pid_task(p, PIDTYPE_PID);
if ( task == NULL )
..
// check ptrace privs
int ret = cap_ptrace_access_check(task, PTRACE_MODE_READ);
When compiling it generates an error:
WARNING: "cap_ptrace_access_check" [$PATH/$MOD.ko] undefined!
I tried with ptrace_access_check, ptrace_may_check,
security_ptrace_access_check, ptrace_may_access, etc... but none of them
works for me. I'm building the module against a 2.6.35 kernel.
Any idea about what am I doing wrong?
Thanks in advance!
Joxean Koret
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120319/1fa075db/attachment.bin
reply other threads:[~2012-03-19 10:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1332151565.12845.89.camel@backup-server \
--to=joxeankoret@yahoo.es \
--cc=kernelnewbies@lists.kernelnewbies.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 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.