On 04/13/2016 02:43 PM, Richard W.M. Jones wrote: > 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 main program might be multithreaded. > > This patch series adds a trivial system call "getumask" which returns > the umask of the current process.
Ah! Thanks for this :) Acked-by: Pavel Emelyanov <[email protected]>
