From: Pavel Emelyanov <xemul@virtuozzo.com>
To: "Richard W.M. Jones" <rjones@redhat.com>, linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
akpm@linux-foundation.org, luto@kernel.org,
viro@zeniv.linux.org.uk, mathieu.desnoyers@efficios.com,
zab@redhat.com, emunson@akamai.com, paulmck@linux.vnet.ibm.com,
aarcange@redhat.com, josh@joshtriplett.org, xemul@parallels.com,
sfr@canb.auug.org.au, milosz@adfin.com, rostedt@goodmis.org,
arnd@arndb.de, ebiederm@xmission.com, gorcunov@openvz.org,
iulia.manda21@gmail.com, dave.hansen@linux.intel.com,
mguzik@redhat.com, adobriyan@gmail.com, dave@stgolabs.net,
linux-api@vger.kernel.org
Subject: Re: [PATCH 0/2] vfs: Define new syscall getumask.
Date: Wed, 13 Apr 2016 15:05:09 +0300 [thread overview]
Message-ID: <570E35F5.90002@virtuozzo.com> (raw)
In-Reply-To: <1460547786-16766-1-git-send-email-rjones@redhat.com>
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@virtuozzo.com>
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Emelyanov <xemul@virtuozzo.com>
To: "Richard W.M. Jones" <rjones@redhat.com>, <linux-kernel@vger.kernel.org>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
<akpm@linux-foundation.org>, <luto@kernel.org>,
<viro@zeniv.linux.org.uk>, <mathieu.desnoyers@efficios.com>,
<zab@redhat.com>, <emunson@akamai.com>,
<paulmck@linux.vnet.ibm.com>, <aarcange@redhat.com>,
<josh@joshtriplett.org>, <xemul@parallels.com>,
<sfr@canb.auug.org.au>, <milosz@adfin.com>, <rostedt@goodmis.org>,
<arnd@arndb.de>, <ebiederm@xmission.com>, <gorcunov@openvz.org>,
<iulia.manda21@gmail.com>, <dave.hansen@linux.intel.com>,
<mguzik@redhat.com>, <adobriyan@gmail.com>, <dave@stgolabs.net>,
<linux-api@vger.kernel.org>
Subject: Re: [PATCH 0/2] vfs: Define new syscall getumask.
Date: Wed, 13 Apr 2016 15:05:09 +0300 [thread overview]
Message-ID: <570E35F5.90002@virtuozzo.com> (raw)
In-Reply-To: <1460547786-16766-1-git-send-email-rjones@redhat.com>
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@virtuozzo.com>
next prev parent reply other threads:[~2016-04-13 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 11:43 [PATCH 0/2] vfs: Define new syscall getumask Richard W.M. Jones
2016-04-13 11:43 ` Richard W.M. Jones
2016-04-13 11:43 ` [PATCH 1/2] " Richard W.M. Jones
[not found] ` <1460547786-16766-2-git-send-email-rjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-04-13 12:21 ` Florian Weimer
2016-04-13 12:21 ` Florian Weimer
[not found] ` <87inzlg0mo.fsf-ZqZwdwZz9NfTBotR3TxKnbNAH6kLmebB@public.gmane.org>
2016-04-13 12:40 ` Cyrill Gorcunov
2016-04-13 12:40 ` Cyrill Gorcunov
2016-04-13 11:43 ` [PATCH 2/2] x86: Wire up new getumask system call on x86 Richard W.M. Jones
[not found] ` <1460547786-16766-3-git-send-email-rjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-04-13 12:36 ` kbuild test robot
2016-04-13 12:36 ` kbuild test robot
2016-04-13 12:05 ` Pavel Emelyanov [this message]
2016-04-13 12:05 ` [PATCH 0/2] vfs: Define new syscall getumask Pavel Emelyanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570E35F5.90002@virtuozzo.com \
--to=xemul@virtuozzo.com \
--cc=aarcange@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=ebiederm@xmission.com \
--cc=emunson@akamai.com \
--cc=gorcunov@openvz.org \
--cc=hpa@zytor.com \
--cc=iulia.manda21@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mguzik@redhat.com \
--cc=milosz@adfin.com \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rjones@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.com \
--cc=zab@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.