[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <570E35F5.90002@virtuozzo.com>
Date: Wed, 13 Apr 2016 15:05:09 +0300
From: Pavel Emelyanov <xemul@...tuozzo.com>
To: "Richard W.M. Jones" <rjones@...hat.com>,
<linux-kernel@...r.kernel.org>
CC: <tglx@...utronix.de>, <mingo@...hat.com>, <hpa@...or.com>,
<akpm@...ux-foundation.org>, <luto@...nel.org>,
<viro@...iv.linux.org.uk>, <mathieu.desnoyers@...icios.com>,
<zab@...hat.com>, <emunson@...mai.com>,
<paulmck@...ux.vnet.ibm.com>, <aarcange@...hat.com>,
<josh@...htriplett.org>, <xemul@...allels.com>,
<sfr@...b.auug.org.au>, <milosz@...in.com>, <rostedt@...dmis.org>,
<arnd@...db.de>, <ebiederm@...ssion.com>, <gorcunov@...nvz.org>,
<iulia.manda21@...il.com>, <dave.hansen@...ux.intel.com>,
<mguzik@...hat.com>, <adobriyan@...il.com>, <dave@...olabs.net>,
<linux-api@...r.kernel.org>
Subject: Re: [PATCH 0/2] vfs: Define new syscall getumask.
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 <xemul@...tuozzo.com>
Powered by blists - more mailing lists