Re: snapd and semaphores

2017-01-16 Thread Mark Shuttleworth
On 10/01/17 08:44, Olivier Tilloy wrote: > On Tue, Jan 10, 2017 at 2:41 PM, Jamie Strandboge wrote: >> On Wed, 2017-01-04 at 13:39 +0100, Olivier Tilloy wrote: >>> Here is the bug report: https://launchpad.net/bugs/1653955 >> Thanks! The fix is in master and will bi in snapd

Re: snapd and semaphores

2017-01-10 Thread Olivier Tilloy
On Tue, Jan 10, 2017 at 2:41 PM, Jamie Strandboge wrote: > On Wed, 2017-01-04 at 13:39 +0100, Olivier Tilloy wrote: >> >> Here is the bug report: https://launchpad.net/bugs/1653955 > > Thanks! The fix is in master and will bi in snapd 2.21. Excellent, thanks Jamie for your

Re: snapd and semaphores

2017-01-10 Thread Jamie Strandboge
On Wed, 2017-01-04 at 13:39 +0100, Olivier Tilloy wrote: >  > Here is the bug report: https://launchpad.net/bugs/1653955 Thanks! The fix is in master and will bi in snapd 2.21. -- Jamie Strandboge | http://www.canonical.com signature.asc Description: This is a digitally signed

Re: snapd and semaphores

2017-01-04 Thread Olivier Tilloy
On Tue, Jan 3, 2017 at 8:21 PM, Jamie Strandboge wrote: > On Mon, 2017-01-02 at 16:34 +0100, Olivier Tilloy wrote: >> Hi everyone, and happy new year! >> >> I’m snapping an app that makes use of semaphores¹ and seeing an >> apparmor denial. The glibc implementation of

Re: snapd and semaphores

2017-01-03 Thread Jamie Strandboge
On Mon, 2017-01-02 at 16:34 +0100, Olivier Tilloy wrote: > Hi everyone, and happy new year! > > I’m snapping an app that makes use of semaphores¹ and seeing an > apparmor denial. The glibc implementation of sem_open calls > SHM_GET_NAME(EINVAL,SEM_FAILED,SEM_SHM_PREFIX) where SEM_SHM_PREFIX is >

snapd and semaphores

2017-01-02 Thread Olivier Tilloy
Hi everyone, and happy new year! I’m snapping an app that makes use of semaphores¹ and seeing an apparmor denial. The glibc implementation of sem_open calls SHM_GET_NAME(EINVAL,SEM_FAILED,SEM_SHM_PREFIX) where SEM_SHM_PREFIX is "sem.", so it tries to create /dev/shm/sem.{name}, which fails