From: devzero@web.de
To: sangshuduo@gmail.com
Cc: bosko.radivojevic@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Inserting code from userspace to kernel space
Date: Fri, 23 May 2008 16:30:16 +0200 [thread overview]
Message-ID: <289344083@web.de> (raw)
>> I know this sounds quite weird, but maybe there is a project that can help us ;)
>>
>
>actually you can implement a parser/interpretor, whatever you name it,
>in kernel space. And you can send the
>function code from user space to kernel space by device driver
>interface. the parser can parse that and do something
>practical function in kernel.
>
>I have worked on a similar task in a product powered by linux. It works great.
any pointer to the sourcecode so bosko (and others) can profit from that ?
List: linux-kernel
Subject: Re: Inserting code from userspace to kernel space
From: "Shuduo Sang" <sangshuduo () gmail ! com>
Date: 2008-05-22 16:04:35
Message-ID: ee101c360805220904h1c69db12q3048d0347d27c461 () mail ! gmail ! com
[Download message RAW]
On Thu, May 22, 2008 at 8:41 PM, Bosko Radivojevic
<bosko.radivojevic@gmail.com> wrote:
> Hi!
>
> I'm looking for a way to insert code from user space to the kernel
> space, but without using kernel module. Actually, we are working on a
> system that has to allow end user to change part of code (one or two
> functions) that is executed from the kernel space.
>
> For now we have two different kernel modules, one exporting a function
> which another module uses. Process of compiling kernel module is quite
> ineligible for standard end user (along with the requirement to
> support multi platform cross compiling) compared to just cross
> compiling a simple code that doesn't use any libraries than libc.
>
> I know this sounds quite weird, but maybe there is a project that can help us ;)
>
actually you can implement a parser/interpretor, whatever you name it,
in kernel space. And you can send the
function code from user space to kernel space by device driver
interface. the parser can parse that and do something
practical function in kernel.
I have worked on a similar task in a product powered by linux. It works great.
> Sincerely,
> Bosko
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
______________________________________________________________
Jeden Monat 1 hochkarätiger maxdome-Blockbuster GRATIS!
Exklusiv für alle WEB.DE Nutzer. http://www.blockbuster.web.de
next reply other threads:[~2008-05-23 14:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 14:30 devzero [this message]
2008-05-25 3:37 ` Inserting code from userspace to kernel space Shuduo Sang
2008-05-25 3:47 ` David Newall
2008-05-25 15:44 ` Shuduo Sang
2008-05-26 9:44 ` Jiri Kosina
2008-05-26 11:49 ` David Newall
-- strict thread matches above, loose matches on Subject: below --
2008-05-25 9:35 devzero
2008-05-25 12:21 ` David Newall
2008-05-25 13:14 ` Tom Spink
2008-05-22 12:41 Bosko Radivojevic
2008-05-22 13:06 ` Jan Engelhardt
2008-05-22 14:31 ` Helge Hafting
2008-05-22 16:04 ` Shuduo Sang
2008-05-25 5:44 ` Alex Belits
2008-05-25 7:18 ` Bart Van Assche
2008-05-26 6:48 ` Geert Uytterhoeven
2008-05-26 9:54 ` Jike Song
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=289344083@web.de \
--to=devzero@web.de \
--cc=bosko.radivojevic@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sangshuduo@gmail.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