From: "Frank Ch. Eigler" <fche@redhat.com>
To: Prasanna S Panchamukhi <prasanna@in.ibm.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
davem@davemloft.net, suparna@in.ibm.com,
richardj_moore@uk.ibm.com, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: RFC - Approaches to user-space probes
Date: Fri, 31 Mar 2006 11:25:14 -0500 [thread overview]
Message-ID: <20060331162514.GB22505@redhat.com> (raw)
In-Reply-To: <20060331115529.GA3501@in.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
Hi -
On Fri, Mar 31, 2006 at 05:25:29PM +0530, Prasanna S Panchamukhi wrote:
> [...]
> > It's pretty clear that writing the dirtied pages to disk is an
> > *undesirable* side-effect, and should be eliminated. [...]
>
> What would the typical situations where the text section in the
> executable is mapped with 'MAP_SHARED'?
Even if such usage is not typical, if it is legal, it may open a
vulnerability. Imagine an unprivileged attacker doing just such an
mmap on some key shared library or executable, hoping that someone
else puts user-kprobes in there.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-03-31 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 6:54 RFC - Approaches to user-space probes Prasanna S Panchamukhi
2006-03-27 7:37 ` Arjan van de Ven
2006-03-27 10:00 ` Prasanna S Panchamukhi
2006-03-27 20:03 ` Arjan van de Ven
2006-03-28 9:42 ` Richard J Moore
2006-03-28 9:47 ` Andi Kleen
2006-03-28 10:10 ` Richard J Moore
2006-03-28 14:54 ` Prasanna S Panchamukhi
2006-03-28 17:29 ` Arjan van de Ven
2006-03-28 20:35 ` Frank Ch. Eigler
2006-03-28 20:44 ` Andi Kleen
2006-03-31 11:55 ` Prasanna S Panchamukhi
2006-03-31 16:25 ` Frank Ch. Eigler [this message]
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=20060331162514.GB22505@redhat.com \
--to=fche@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=prasanna@in.ibm.com \
--cc=richardj_moore@uk.ibm.com \
--cc=suparna@in.ibm.com \
--cc=tytso@mit.edu \
/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.