Missing fork() handling and pitfalls #10

Yeni Konu

crtxcr · 2021-08-09T20:17:19+02:00

crtxcr

2021-08-09 20:17:19 +02:00

yorum yaptı

Sahibi

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.

crtxcr

bug

enhancement

etiketlerini 2021-08-09 20:17:19 +02:00 ekledi

crtxcr

2022-07-17 13:01:24 +02:00

işlemesinde bu konuyu işaret etti

Close file fds by default, introduce policy->keep_fds_open

Bu konuşmaya katılmak için oturum aç.