Re: [PATCH] ipc/shm: properly return EIDRM in shm_lock()

2018-09-25 Thread Kees Cook
On Tue, Sep 25, 2018 at 5:00 AM, Arnd Bergmann wrote: > On Fri, Aug 24, 2018 at 5:09 AM Davidlohr Bueso wrote: >> >> When getting rid of the general ipc_lock(), this was missed >> furthermore, making the comment around the ipc object validity >> check bogus. Under EIDRM conditions, callers will

Re: [PATCH] ipc/shm: properly return EIDRM in shm_lock()

2018-09-25 Thread Kees Cook
On Tue, Sep 25, 2018 at 5:00 AM, Arnd Bergmann wrote: > On Fri, Aug 24, 2018 at 5:09 AM Davidlohr Bueso wrote: >> >> When getting rid of the general ipc_lock(), this was missed >> furthermore, making the comment around the ipc object validity >> check bogus. Under EIDRM conditions, callers will

Re: [PATCH] ipc/shm: properly return EIDRM in shm_lock()

2018-09-25 Thread Arnd Bergmann
On Fri, Aug 24, 2018 at 5:09 AM Davidlohr Bueso wrote: > > When getting rid of the general ipc_lock(), this was missed > furthermore, making the comment around the ipc object validity > check bogus. Under EIDRM conditions, callers will in turn not > see the error and continue with the operation.

Re: [PATCH] ipc/shm: properly return EIDRM in shm_lock()

2018-09-25 Thread Arnd Bergmann
On Fri, Aug 24, 2018 at 5:09 AM Davidlohr Bueso wrote: > > When getting rid of the general ipc_lock(), this was missed > furthermore, making the comment around the ipc object validity > check bogus. Under EIDRM conditions, callers will in turn not > see the error and continue with the operation.

[PATCH] ipc/shm: properly return EIDRM in shm_lock()

2018-08-23 Thread Davidlohr Bueso
When getting rid of the general ipc_lock(), this was missed furthermore, making the comment around the ipc object validity check bogus. Under EIDRM conditions, callers will in turn not see the error and continue with the operation. Fixes: 82061c57ce9 (ipc: drop ipc_lock()) Signed-off-by:

[PATCH] ipc/shm: properly return EIDRM in shm_lock()

2018-08-23 Thread Davidlohr Bueso
When getting rid of the general ipc_lock(), this was missed furthermore, making the comment around the ipc object validity check bogus. Under EIDRM conditions, callers will in turn not see the error and continue with the operation. Fixes: 82061c57ce9 (ipc: drop ipc_lock()) Signed-off-by: