One of the nasty obstacles is that Linux allocs/frees struct cred rather than just having these fields in the task structure.
-
-
-
Presumably the original motive for separate struct cred was that it was big and shared between tasks with same creds.
-
But now (presumably for RCU purposes) every cred change involves alloc/free, no sharing... SO JUST PUT IT BACK IN THE TASK STRUCT FFS!
-
Am I missing some reason why they can't/won't put struct cred in the task struct where it belongs and eliminate ENOMEM failures for setuid?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.