Today I've been trying to understand what's needed to make Linux do multi-threaded setuid right in kernelspace. (http://ewontfix.com/17/ )
-
-
Replying to @RichFelker
One of the nasty obstacles is that Linux allocs/frees struct cred rather than just having these fields in the task structure.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
Presumably the original motive for separate struct cred was that it was big and shared between tasks with same creds.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
But now (presumably for RCU purposes) every cred change involves alloc/free, no sharing... SO JUST PUT IT BACK IN THE TASK STRUCT FFS!
1 reply 0 retweets 0 likes
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?
12:09 PM - 8 Jun 2015
0 replies
0 retweets
0 likes
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.