DAOS-18779 client: reset per-thread based variable after fork - b28#17936
DAOS-18779 client: reset per-thread based variable after fork - b28#17936Nasf-Fan wants to merge 1 commit intorelease/2.8from
Conversation
|
Ticket title is 'Per-thread based variables maybe stable for the child process after fork' |
Nasf-Fan
force-pushed
the
Nasf-Fan/DAOS-18779_b28
branch
3 times, most recently
from
35cc870 to
2e61649
Compare
|
Test stage Functional Hardware Large MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17936/3/execution/node/1329/log |
|
Test stage Functional Hardware Medium MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17936/3/execution/node/1278/log |
Nasf-Fan
force-pushed
the
Nasf-Fan/DAOS-18779_b28
branch
from
2e61649 to
6135ca3
Compare
|
Test stage Functional Hardware Medium MD on SSD completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17936/5/testReport/ |
test_dfuse_daos_build_wb failed for DAOS-18813, not related with the patch. |
Nasf-Fan
force-pushed
the
Nasf-Fan/DAOS-18779_b28
branch
2 times, most recently
from
caa7d40 to
1c97cc7
Compare
|
Test stage Functional Hardware Medium Verbs Provider MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17936/9/execution/node/419/log |
|
Test stage Functional Hardware Medium MD on SSD completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17936/9/testReport/ |
Nasf-Fan
force-pushed
the
Nasf-Fan/DAOS-18779_b28
branch
from
1c97cc7 to
6fb1d12
Compare
|
Test stage Functional Hardware Medium MD on SSD completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17936/10/testReport/ |
DAOS maintains some per-thread based variables on client. They are usually used to distinguish current process from the others. If application creates new process (such as via fork()), these per-thread variables will inherit the values from parents, and if without reset, we cannot distinguish the children processes from the parents via these per-thread based variables. That is not only confused but also may cause correctness issues. The patch offers related reset interfaces, and application can trigger them via after_fork() callback. Allow-unstable-test: true Signed-off-by: Fan Yong <fan.yong@hpe.com>
Nasf-Fan
force-pushed
the
Nasf-Fan/DAOS-18779_b28
branch
from
6fb1d12 to
efef39a
Compare
3 participants
DAOS maintains some per-thread based variables on client. They are usually used to distinguish current process from the others. If application creates new process (such as via fork()), these per-thread variables will inherit the values from parents, and if without reset, we cannot distinguish the children processes from the parents via these per-thread based variables. That is not only confused but also may cause correctness issues.
The patch offers related reset interfaces, and application can trigger them via after_fork() callback.
Allow-unstable-test: true
Steps for the author:
After all prior steps are complete: