Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.1.45, 10.2.32, 10.3.23, 10.4.13, 10.5.4
-
None
Description
MariaDB reads the UMASK and UMASK_DIR environment variables to determine what permissions to use when creating new files.
However, these environment variables are not actually used as umasks. They are just used as regular file system permission modes.
You can see the environment variables are read here:
https://github.com/MariaDB/server/blob/mariadb-10.5.4/mysys/my_init.c#L83
And then they are used as the mode argument when creating new files with open() here:
https://github.com/MariaDB/server/blob/mariadb-10.5.4/mysys/my_open.c#L55
This is pretty confusing behavior. If the environment variables have UMASK in the name, then shouldn't they be used as umasks? And if the environment variables are used as file system permission modes, then shouldn't the names reflect that?
Attachments
Issue Links
- relates to
-
-
- Closed
-
- links to
Activity
| Field | Original Value | New Value |
|---|---|---|
| Remote Link | This issue links to "MySQL Bug #35090 - umask applied as bitmap instead of as a mask (Web Link)" [ 29900 ] |
| Fix Version/s | N/A [ 14700 ] |
| Resolution | Won't Fix [ 2 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Link |
This issue relates to |
| Workflow | MariaDB v3 [ 110719 ] | MariaDB v4 [ 158042 ] |
Right, but what can we do about it? It was like this forever, for 20 years at least, and users rely on this behavior.