Thread (18 messages) 18 messages, 7 authors, 2019-05-16

Re: [PATCH 1/2] pid: add pidfd_open()

From: Aleksa Sarai <hidden>
Date: 2019-05-15 14:51:52
Also in: linux-alpha, linux-api, linux-arch, linux-arm-kernel, linux-kselftest, linux-mips, linux-s390, linux-sh, lkml, sparclinux

On 2019-05-15, Christian Brauner [off-list ref] wrote:
On Wed, May 15, 2019 at 04:00:20PM +0200, Yann Droneaud wrote:
quoted
Would it be possible to create file descriptor with "restricted"
operation ?

- O_RDONLY: waiting for process completion allowed (for example)
- O_WRONLY: sending process signal allowed
Yes, something like this is likely going to be possible in the future.
We had discussion around this. But mapping this to O_RDONLY and O_WRONLY
is not the right model. It makes more sense to have specialized flags
that restrict actions.
Not to mention that the O_* flags have silly values which we shouldn't
replicate in new syscalls IMHO.

-- 
Aleksa Sarai
Senior Software Engineer (Containers)
SUSE Linux GmbH
<https://www.cyphar.com/>

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help