From: David Wilder <dwilder@us.ibm.com>
To: systemtap@sources.redhat.com
Subject: Preventing a tapscript from accessing user space.
Date: Tue, 06 Feb 2007 00:07:00 -0000 [thread overview]
Message-ID: <45C7CE21.6090103@us.ibm.com> (raw)
What prevents a tapscript from attempting to access user space
directly? For example:
if $arg is a pointer to a struct in user space (presumably passed to
the kernel via some system call).
What prevents me from doing i=$arg->j in the tapscript.
Also when I looked at the code generated by stap I was hoping to see
deref() used but that is not what I found.
I could have missed something...
On i386 the above example works ok because we can just access the user
space, it works but it is not correct.
On s390 I can't do that I must use something like get_user(), but I
cant do that ether because get_user() calls might_sleep() and the probe
is running with interrupts off.
--
David Wilder
IBM Linux Technology Center
Beaverton, Oregon, USA
dwilder@us.ibm.com
(503)578-3789
next reply other threads:[~2007-02-06 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 0:07 David Wilder [this message]
2007-06-10 17:23 ` Frank Ch. Eigler
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=45C7CE21.6090103@us.ibm.com \
--to=dwilder@us.ibm.com \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).