Re: [PATCH v3 0/2] vfs: Define new syscall getumask.

2016-04-13 Thread Mathieu Desnoyers
- On Apr 13, 2016, at 3:06 PM, Richard W.M. Jones rjo...@redhat.com wrote: > On Wed, Apr 13, 2016 at 11:52:53AM -0700, Davidlohr Bueso wrote: >> ENOMANPAGE > > Where do man pages go? In the man-pages project? Yes. I usually also put a rendered version of the man page after the changelog of

Re: [PATCH v3 0/2] vfs: Define new syscall getumask.

2016-04-13 Thread Richard W.M. Jones
On Wed, Apr 13, 2016 at 11:52:53AM -0700, Davidlohr Bueso wrote: > ENOMANPAGE Where do man pages go? In the man-pages project? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestf

Re: [PATCH v3 0/2] vfs: Define new syscall getumask.

2016-04-13 Thread Davidlohr Bueso
ENOMANPAGE

Re: [PATCH v3 0/2] vfs: Define new syscall getumask.

2016-04-13 Thread Cyrill Gorcunov
On Wed, Apr 13, 2016 at 02:57:55PM +0100, Richard W.M. Jones wrote: > v2 -> v3: > > - Add the syscall to uapi/asm-generic/unistd.h. > > - Retest. Reviewed-by: Cyrill Gorcunov Thank you!

[PATCH v3 0/2] vfs: Define new syscall getumask.

2016-04-13 Thread Richard W.M. Jones
v2 -> v3: - Add the syscall to uapi/asm-generic/unistd.h. - Retest. -- It's not possible to read the process umask without also modifying it, which is what umask(2) does. A library cannot read umask safely, especially if the