Bug #2357
open(2) flagspace is full
| Status: | Resolved | Start date: | 04/28/2012 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| Category: | - | |||
| Target version: | - |
Description
Recent software expects to be able to use open with flags such as O_DIRECTORY or O_CLOEXEC; they are useful to prevent races and securities vulnerabilities.
I have looked at implementing O_CLOEXEC support, but all the bits in an int are already used; I have counted about 10 DragonFly-specific flags in the lot.
The standard flags, as defined in the current POSIX.1-2008 standard:
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/fcntl.h.html
Related todos
Related issues
History
Updated by ftigeot 10 months ago
O_ROOTCRED is DragonFly-specific and effectively unused.
It can be removed without causing secondary issues
Updated by ftigeot 10 months ago
- % Done changed from 0 to 10
O_FRNONBLOCKING is also effectively unused
Updated by ftigeot 10 months ago
- File 0001-kernel-remove-O_ROOTCRED.patch added
- File 0002-kernel-remove-O_FRNONBLOCKING.patch added
Patches to remove O_ROOTCRED and O_FRNONBLOCKING
Complete world+kernel builds are needed