From: Timo Benk <t_benk@web.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Timo Benk <t_benk@web.de>
Subject: Re: allocate memory in userspace (Answer)
Date: Tue, 2 Jul 2002 12:24:42 +0200 [thread overview]
Message-ID: <20020702102442.GB9965@toshiba> (raw)
In-Reply-To: <20020702075117.GA5604@toshiba>
As stated by Andy Kleen this is not a good solution.
This is his post to the topic:
----<snip>----
> I am a kernel newbie and i am writing a module. I
> need to allocate some memory in userspace because
> i want to access syscalls like open(), lstat() etc.
> I need to call these methods in the kernel, and in
> my special case there is no other way, but i
> do not want to reimplement all the syscalls.
>
> I read that it should be possible, but i cannot
> find any example or recipe on how to do it.
mm_segment_t oldfs = get_fs();
set_fs(KERNEL_DS);
ret = sys_yoursyscall(kernelargs ...)
set_fs(oldfs);
Do not even think about using mmap or accessing sys_call_table for this.
Your other post was so tasteless that it would be good if you retracted
it with a followup because it would be very bad to have such an bad
example
in the l-k archives open to innocent search machine users uncommented.
-Andi
-
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/
----<snap>-----
On Tue, Jul 02, 2002 at 09:51:17AM +0200, Timo Benk wrote:
> Hi,
>
> I found the following function in arch/i386/kernel/sys_i386.c:
>
> ---<snip>---
> /* common code for old and new mmaps */
> long do_mmap2
> (
> unsigned long addr, unsigned long len,
> unsigned long prot, unsigned long flags,
> unsigned long fd, unsigned long pgoff
> )
> {
> int error = -EBADF;
> struct file * file = NULL;
>
> flags &= ~(MAP_EXECUTABLE | MAP_DENYWRITE);
> if (!(flags & MAP_ANONYMOUS)) {
> file = fget(fd);
> if (!file)
> goto out;
> }
>
> down_write(¤t->mm->mmap_sem);
> error = do_mmap_pgoff(file, addr, len, prot, flags, pgoff);
> up_write(¤t->mm->mmap_sem);
>
> if (file)
> fput(file);
> out:
> return error;
> }
> ---<snap>---
>
> the following code works for me(of course
> don't forget to munmap the memory).
> ---<snip>---
> char *userspace;
> char kernelspace[2048];
>
> userspace = (char*)do_mmap2
> (
> 0,
> 2048,
> PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANON,
> -1,
> 0
> );
>
> copy_to_user( userspace, "/dev/hda", 9 );
>
> copy_from_user( kernelspace, userspace, 9 );
> printk("%s\n",kernelspace);
> ---<snap>---
>
> Hope that helps any other struggling newbie:-)
>
> -timo
>
> --
> gpg key fingerprint = 6832 C8EC D823 4059 0CD1 6FBF 9383 7DBD 109E 98DC
>
--
gpg key fingerprint = 6832 C8EC D823 4059 0CD1 6FBF 9383 7DBD 109E 98DC
next prev parent reply other threads:[~2002-07-02 10:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 17:26 allocate memory in userspace Timo Benk
2002-07-01 17:49 ` Erik Andersen
2002-07-02 8:37 ` William Lee Irwin III
2002-07-02 8:44 ` William Lee Irwin III
2002-07-02 9:00 ` Erik Andersen
2002-07-01 18:39 ` Calin A. Culianu
2002-07-02 7:51 ` allocate memory in userspace (Answer) Timo Benk
2002-07-02 10:24 ` Timo Benk [this message]
2002-07-02 12:19 ` allocate memory in userspace Brian Gerst
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=20020702102442.GB9965@toshiba \
--to=t_benk@web.de \
--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
all inboxes | Powered by JetHome®