lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 19 Jan 2008 12:12:10 -0300
From:	"Rafael Sisto" <>
To:	"Jan Engelhardt" <>
Cc:	"Linux kernel" <>
Subject: Re: new file in kernel.

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;
       return 0;

what do you think??

Greetings, Rafael Sisto

On Jan 19, 2008 11:30 AM, Jan Engelhardt <> 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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists