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 添加了标签
bug
enhancement
登录 并参与到对话中。
未选择里程碑
未指派成员
1 名参与者
通知
到期时间
到期日期无效或超出范围。请使用 'yyyy-mm-dd' 格式。

未设置到期时间。

依赖工单

没有设置依赖项。

参考:crtxcr/exile.h#10
没有提供说明。