[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87shypck6m.fsf@mid.deneb.enyo.de>
Date: Wed, 13 Apr 2016 22:45:05 +0200
From: Florian Weimer <fw@...eb.enyo.de>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: "Richard W.M. Jones" <rjones@...hat.com>,
linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
akpm@...ux-foundation.org, luto@...nel.org,
viro@...iv.linux.org.uk, mathieu.desnoyers@...icios.com,
zab@...hat.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, gorcunov@...il.com, walters@...bum.org
Subject: Re: [PATCH v4 0/3] vfs: Define new syscall umask2 [formerly getumask]
* H. Peter Anvin:
> I have to say I'm skeptic to the need for umask2() as opposed to
> getumask().
I find the extension with a set-the-thread umask somewhat unlikely.
How would a potential per-thread umask interact with CLONE_FS?
Have a per-thread umask that, when active, overrides the global
one, similar to what uselocale provides? That seems rather messy,
and I'm not aware of any precedent.
Powered by blists - more mailing lists