Missing fork() handling and pitfalls #10

开启中
crtxcr2021-08-09 20:17:19 +02:00创建 · 0 评论
所有者

We don't do fork()/clone() ourselves, opening the door for many pitfalls, e. g. we inherit open file descriptories which may enable bypassing of the policies we set. Otoh, some open fd's may actually be desired.

We must either offer a safe fork()/clone() or check that the current process is in a reasonable state and/or transform to that state.

We don't do fork()/clone() ourselves, opening the door for many pitfalls, e. g. we inherit open file descriptories which may enable bypassing of the policies we set. Otoh, some open fd's may actually be desired. We must either offer a safe fork()/clone() or check that the current process is in a reasonable state and/or transform to that state.
crtxcr2021-08-09 20:17:19 +02:00 添加标签 bugenhancement
登录 并参与到对话中。
1 名参与者
通知
截止日期
未设置截止日期。
依赖工单

未设置依赖工单。

引用:crtxcr/exile.h#10