From: Hugh Dickins <hugh@veritas.com>
To: Prasanna S Panchamukhi <prasanna@in.ibm.com>
Cc: linux-kernel@vger.kernel.org, systemtap@sources.redhat.com,
akpm@osdl.org, Andi Kleen <ak@suse.de>,
davem@davemloft.net, suparna@in.ibm.com,
richardj_moore@uk.ibm.com, hch@infradead.org
Subject: Re: [RFC] [PATCH 6/6] Kprobes: Remove breakpoints from the copied pages
Date: Tue, 9 May 2006 18:04:50 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0605091747050.10238@blonde.wat.veritas.com> (raw)
In-Reply-To: <20060509071523.GF22493@in.ibm.com>
On Tue, 9 May 2006, Prasanna S Panchamukhi wrote:
> This patch removes the breakpoints if the pages read from the page
> cache contains breakpoints. If the pages containing the breakpoints
> is copied from the page cache, the copied image would also contain
> breakpoints in them. This could be a major problem for tools like
> tripwire etc and cause security concerns, hence must be prevented.
> This patch hooks up the actor routine, checks if the executable was
> a probed executable using the file inode and then replaces the
> breakpoints with the original opcodes in the copied image.
You've done a nice job of making the code look like kernel code
throughout, it's a much tidier patchset than many.
With that said... it looks to me like one of the scariest and
most inappropriate sets I can remember. Getting the kernel to
connive in presenting an incoherent view of its pagecache:
I don't think we'd ever want that.
There's all kinds of things that could be said about the details
(your locking is often insufficient, for example); but there's a
lot going on, and it doesn't seem worth going through this line
by line, when the whole concept seems so unwelcome.
You've a big task to convince people that this is something the
Linux kernel will want: and perhaps you'll succeed - good luck.
But please approach what you're trying to do from userspace:
you can patch the binaries from there if you wish (but not on
my system, thanks). Or perhaps you can patch it all into the
kernel via kprobes itself, but I wouldn't recommend it.
Hugh
next prev parent reply other threads:[~2006-05-09 17:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 6:54 [RFC] [PATCH 0/6] Kprobes: User-space probes support for i386 Prasanna S Panchamukhi
2006-05-09 6:59 ` [RFC] [PATCH 1/6] Kprobes: Allow/deny exclusive write access to inodes Prasanna S Panchamukhi
2006-05-09 7:01 ` [RFC] [PATCH 2/6] Kprobes: Get one pagetable entry Prasanna S Panchamukhi
2006-05-09 7:05 ` [RFC] [PATCH 3/6] Kprobes: New interfaces for user-space probes Prasanna S Panchamukhi
2006-05-09 7:09 ` [RFC] [PATCH 4/6] Kprobes: Insert probes on non-memory resident pages Prasanna S Panchamukhi
2006-05-09 7:12 ` [RFC] [PATCH 5/6] Kprobes: Single step the original instruction out-of-line Prasanna S Panchamukhi
2006-05-09 7:15 ` [RFC] [PATCH 6/6] Kprobes: Remove breakpoints from the copied pages Prasanna S Panchamukhi
2006-05-09 17:04 ` Hugh Dickins [this message]
2006-05-10 12:17 ` Prasanna S Panchamukhi
2006-05-10 15:17 ` Hugh Dickins
2006-05-09 9:38 ` [RFC] [PATCH 5/6] Kprobes: Single step the original instruction out-of-line Christoph Hellwig
2006-05-10 0:47 ` bibo,mao
2006-05-10 14:19 ` Richard J Moore
2006-05-09 9:37 ` [RFC] [PATCH 4/6] Kprobes: Insert probes on non-memory resident pages Christoph Hellwig
2006-05-09 9:36 ` [RFC] [PATCH 3/6] Kprobes: New interfaces for user-space probes Christoph Hellwig
2006-05-09 15:11 ` Richard J Moore
2006-05-09 15:18 ` Christoph Hellwig
2006-05-09 17:41 ` Frank Ch. Eigler
2006-05-09 20:40 ` Adrian Bunk
2006-05-09 20:58 ` Frank Ch. Eigler
2006-05-09 22:35 ` Christoph Hellwig
2006-05-09 9:34 ` [RFC] [PATCH 2/6] Kprobes: Get one pagetable entry Christoph Hellwig
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=Pine.LNX.4.64.0605091747050.10238@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
--cc=richardj_moore@uk.ibm.com \
--cc=suparna@in.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
all inboxes | Powered by JetHome®