Re: [PATCH v2 1/3] shm: add sealing API

2014-06-02 Thread Hugh Dickins
On Fri, 23 May 2014, David Herrmann wrote: > > i_mmap_mutex is the only per-object lock that is taken in the mmap() > path and all vma_link() users can easily be changed to deal with > errors. So I think it should be easy to make __vma_link_file() fail if > no writable mappings are allowed. Testin

Re: [PATCH v2 1/3] shm: add sealing API

2014-05-23 Thread David Herrmann
Hi Hugh Thanks for the review! Looks all good, few comments inline in case I didn't agree. Everything else I didn't comment on is fixed in my tree. On Tue, May 20, 2014 at 4:16 AM, Hugh Dickins wrote: > On Tue, 15 Apr 2014, David Herrmann wrote: >> diff --git a/include/linux/shmem_fs.h b/include

Re: [PATCH v2 1/3] shm: add sealing API

2014-05-19 Thread Hugh Dickins
On Tue, 15 Apr 2014, David Herrmann wrote: > If two processes share a common memory region, they usually want some > guarantees to allow safe access. This often includes: > - one side cannot overwrite data while the other reads it > - one side cannot shrink the buffer while the other accesses

[PATCH v2 1/3] shm: add sealing API

2014-04-15 Thread David Herrmann
If two processes share a common memory region, they usually want some guarantees to allow safe access. This often includes: - one side cannot overwrite data while the other reads it - one side cannot shrink the buffer while the other accesses it - one side cannot grow the buffer beyond previo