mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael Sisto" <rafael.sisto@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: "Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: new file in kernel.
Date: Sat, 19 Jan 2008 12:12:10 -0300	[thread overview]
Message-ID: <ee3dc96c0801190712v56bcfde5qa015888f2bcbde98@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801191526200.27831@fbirervta.pbzchgretzou.qr>

Dear Jan,

The idea of the indirection is to make it transparent for the user.
The idea is to do almost the same as what IPC does. The user calls
"get", then "attach". In the "get" syscall I create a tmp file and
return some id. Then the user calls an "attach" syscall with the
returned id.

The result is that he gets a shared memorymapped to his vma.

Is my idea clearer now?

As for the snippet, thank you. But I read somewhere that it is not
recommended to call system calls inside another system call, right?

So, I think somthing like this code would do, right?

asmlinkage long sys_my_shmget(int size)
{
       long ret;

       ret = sys_open("/tmp/shmfile", O_CREAT | O_RDWR  , 777);
       if (ret < 0)
               return ret;
       sys_close(fd);
       return 0;
}

what do you think??



Greetings, Rafael Sisto

On Jan 19, 2008 11:30 AM, Jan Engelhardt <jengelh@computergmbh.de> wrote:
>
> On Jan 19 2008 11:08, Rafael Sisto wrote:
> >
> >I had already read that webpage, but I dont need to change the data on
> >that file. I just want to create a new file and then close it, so I
> >can use it later in another system call, to mmap it to a user space.
> >Is it clearer now?
> >Can you please give me some code snippet?
>
> I don't get what your indirection is supposed to do.
>
>  userspace -> sys_open -> kernel space -> create file
>            -> sys_close -> kernel space -> close it
>
> vs
>
>  userspace -> sys_mycall -> kernelspace -> sys_open -> create_file
>                                         -> sys_close -> create_file
>
> As for code snippets:
>
> asmlinkage logn sys_mycall(const char __user *filename,
>     unsigned int flags, unsigned int mode)
> {
>         long ret;
>
>         ret = sys_open(filename, flags, mode);
>         if (ret < 0)
>                 return ret;
>
>         return sys_close(fd);
> }
>
> You see, this is currently just too trivial to make sense, but if
> it helps you, no problem.
>
> >Sorry for the last mail, I answered to your personal mail only)
>
> Here, we use Reply-to-all.
>
>

  reply	other threads:[~2008-01-19 15:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19 13:42 Rafael Sisto
2008-01-19 13:48 ` Arnaldo Carvalho de Melo
2008-01-19 14:21   ` Rafael Sisto
2008-01-19 14:30     ` Jan-Benedict Glaw
2008-01-19 14:57       ` Rafael Sisto
2008-01-19 15:26         ` Stefan Richter
2008-01-19 16:15           ` Rafael Sisto
2008-01-19 16:23             ` Arnaldo Carvalho de Melo
2008-01-19 17:57             ` Stefan Richter
2008-01-19 13:49 ` Jan Engelhardt
2008-01-19 14:08   ` Rafael Sisto
2008-01-19 14:30     ` Jan Engelhardt
2008-01-19 15:12       ` Rafael Sisto [this message]
2008-01-20  1:29         ` Jan-Benedict Glaw
2008-01-21 13:00           ` Rafael Sisto

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=ee3dc96c0801190712v56bcfde5qa015888f2bcbde98@mail.gmail.com \
    --to=rafael.sisto@gmail.com \
    --cc=jengelh@computergmbh.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

Powered by JetHome