public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Piotr Muszynski <piotru@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Joel.Becker@oracle.com
Subject: Re: module for controlling kprobes with /proc
Date: Mon, 4 Apr 2005 18:40:22 +0900	[thread overview]
Message-ID: <c0310912050404024062a183b8@mail.gmail.com> (raw)

Joel Becker wrote:
>> I have programmed a universal module to register/remove kprobes handlers
>> by interacting with /proc with simple commands.
>
>
>	Looking at your code, I'm thinking you could really use
>configfs.  With configfs, kernelspace objects are created and controlled
>via regular filesystem operations.  Instead of echoing a cryptic line to
>your proc file, a user could instead create objects in a directory:
>
>To insert a handler:
>	cd /config/kprobes
>	mkdir myhandler
>	cd myhandler
>	echo 0x12345678 > handler_address
>	echo 0x87654321 > breakpoint_address
>	echo post > when
>
>To remove one:
>	cd /config/kprobes
>	rmdir myhandler
>
>	If this interests you at all, see
>http://oss.oracle.com/projects/ocfs2/src/trunk/fs/configfs/,
>specifically configfs.txt and configfs_example.c.  I'm going to be
>submitting this for mainline inclusion soon.

Joel,  thank you very much - this looks like a Good Idea. I am going
to try configfs  as soon as my schedule permits.
(Will be grateful for any directions, as I'm new in kernelspace :-))

Piotr
PS Hope you don't mind me quoting your message here.

             reply	other threads:[~2005-04-04  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04  9:40 Piotr Muszynski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-04  8:35 module for controlling kprobes with /proc Prasanna S Panchamukhi
2005-04-04  9:55 ` Piotr Muszynski
2005-03-31 11:54 Piotr Muszynski

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=c0310912050404024062a183b8@mail.gmail.com \
    --to=piotru@gmail.com \
    --cc=Joel.Becker@oracle.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox