From: Dave Jones <davej@codemonkey.org.uk>
To: Andi Kleen <ak@suse.de>
Cc: "Vamsi Krishna S ." <vamsi@in.ibm.com>,
torvalds@transmeta.com, lkml <linux-kernel@vger.kernel.org>,
dprobes <dprobes@www-124.southbury.usf.ibm.com>,
richard <richardj_moore@uk.ibm.com>, tom <hanrahat@us.ibm.com>
Subject: Re: [PATCH] kprobes for 2.5.50-bk2
Date: Tue, 3 Dec 2002 13:26:21 +0000 [thread overview]
Message-ID: <20021203132621.GA811@suse.de> (raw)
In-Reply-To: <p734r9vtg62.fsf@oldwotan.suse.de>
On Tue, Dec 03, 2002 at 01:56:05PM +0100, Andi Kleen wrote:
> > This last part just got me thinking.
> > What stops someone for example using this to implement a binary
> > only replacement of the TCP/IP stack, or any other part of the
> > kernel for that matter ?
>
> It can be already easily done, just patch the kernel code in /dev/kmem
> and add some jump instructions to your loaded module.
> But it's not practical, because it's 100% binary dependent and would
> break with every small change.
indeed.
> Similar to kprobes. But kprobes is actually useful for kernel debugging/
> tracing and unlike many other of these patches not very intrusive.
Suparna also just told me I overlooked the _GPL on the export.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-12-03 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021203125447.A2951@in.ibm.com.suse.lists.linux.kernel>
[not found] ` <20021203121858.GC30431@suse.de.suse.lists.linux.kernel>
2002-12-03 12:56 ` Andi Kleen
2002-12-03 13:26 ` Dave Jones [this message]
2002-12-03 7:24 Vamsi Krishna S .
2002-12-03 12:18 ` Dave Jones
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=20021203132621.GA811@suse.de \
--to=davej@codemonkey.org.uk \
--cc=ak@suse.de \
--cc=dprobes@www-124.southbury.usf.ibm.com \
--cc=hanrahat@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richardj_moore@uk.ibm.com \
--cc=torvalds@transmeta.com \
--cc=vamsi@in.ibm.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
Powered by JetHome