Actions
Bug #2357
closed
open(2) flagspace is full
Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
04/28/2012
Due date:
% Done:
100%
Estimated time:
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
Files
Updated by ftigeot over 12 years ago
O_ROOTCRED is DragonFly-specific and effectively unused.
It can be removed without causing secondary issues
Updated by ftigeot over 12 years ago
- % Done changed from 0 to 10
O_FRNONBLOCKING is also effectively unused
Actions
#3
Updated by ftigeot over 12 years ago
- File 0001-kernel-remove-O_ROOTCRED.patch 0001-kernel-remove-O_ROOTCRED.patch added
- File 0002-kernel-remove-O_FRNONBLOCKING.patch 0002-kernel-remove-O_FRNONBLOCKING.patch added
Patches to remove O_ROOTCRED and O_FRNONBLOCKING
Complete world+kernel builds are needed
Updated by ftigeot over 12 years ago
- Status changed from New to Resolved
- % Done changed from 10 to 100
Both patches pushed today
Actions