[PATCH 3/6] shm: add memfd_create() syscall

2014-04-10 Thread Andy Lutomirski
On 04/02/2014 06:38 AM, Konstantin Khlebnikov wrote: > On Wed, Mar 19, 2014 at 11:06 PM, David Herrmann > wrote: >> memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor >> that you can pass to mmap(). It explicitly allows sealing and >> avoids any connection to user-visible

[PATCH 3/6] shm: add memfd_create() syscall

2014-04-02 Thread Konstantin Khlebnikov
On Wed, Apr 2, 2014 at 6:18 PM, David Herrmann wrote: > Hi > > On Wed, Apr 2, 2014 at 3:38 PM, Konstantin Khlebnikov > wrote: >> On Wed, Mar 19, 2014 at 11:06 PM, David Herrmann >> wrote: >>> memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor >>> that you can pass to mm

[PATCH 3/6] shm: add memfd_create() syscall

2014-04-02 Thread Konstantin Khlebnikov
On Wed, Mar 19, 2014 at 11:06 PM, David Herrmann wrote: > memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor > that you can pass to mmap(). It explicitly allows sealing and > avoids any connection to user-visible mount-points. Thus, it's not > subject to quotas on mounted

[PATCH 3/6] shm: add memfd_create() syscall

2014-04-02 Thread David Herrmann
Hi On Wed, Apr 2, 2014 at 3:38 PM, Konstantin Khlebnikov wrote: > On Wed, Mar 19, 2014 at 11:06 PM, David Herrmann > wrote: >> memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor >> that you can pass to mmap(). It explicitly allows sealing and >> avoids any connection to

[PATCH 3/6] shm: add memfd_create() syscall

2014-03-20 Thread Pavel Emelyanov
On 03/20/2014 03:29 PM, David Herrmann wrote: > Hi > > On Thu, Mar 20, 2014 at 10:01 AM, Pavel Emelyanov > wrote: >> On 03/20/2014 12:47 PM, Cyrill Gorcunov wrote: >>> If I'm not mistaken in something obvious, this looks similar to >>> /proc/pid/map_files >>> feature, Pavel? >> >> It is, but th

[PATCH 3/6] shm: add memfd_create() syscall

2014-03-20 Thread Pavel Emelyanov
On 03/20/2014 12:47 PM, Cyrill Gorcunov wrote: > On Wed, Mar 19, 2014 at 08:06:48PM +0100, David Herrmann wrote: >> memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor >> that you can pass to mmap(). It explicitly allows sealing and >> avoids any connection to user-visible mo

[PATCH 3/6] shm: add memfd_create() syscall

2014-03-20 Thread Cyrill Gorcunov
On Wed, Mar 19, 2014 at 08:06:48PM +0100, David Herrmann wrote: > memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor > that you can pass to mmap(). It explicitly allows sealing and > avoids any connection to user-visible mount-points. Thus, it's not > subject to quotas on mo

[PATCH 3/6] shm: add memfd_create() syscall

2014-03-20 Thread David Herrmann
Hi On Thu, Mar 20, 2014 at 10:01 AM, Pavel Emelyanov wrote: > On 03/20/2014 12:47 PM, Cyrill Gorcunov wrote: >> If I'm not mistaken in something obvious, this looks similar to >> /proc/pid/map_files >> feature, Pavel? > > It is, but the map_files will work "in the opposite direction" :) In the

[PATCH 3/6] shm: add memfd_create() syscall

2014-03-20 Thread John Stultz
On 03/19/2014 12:06 PM, David Herrmann wrote: > memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor > that you can pass to mmap(). It explicitly allows sealing and > avoids any connection to user-visible mount-points. Thus, it's not > subject to quotas on mounted file-systems

[PATCH 3/6] shm: add memfd_create() syscall

2014-03-19 Thread David Herrmann
memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor that you can pass to mmap(). It explicitly allows sealing and avoids any connection to user-visible mount-points. Thus, it's not subject to quotas on mounted file-systems, but can be used like malloc()'ed memory, but with a