On a same connection, a worker can send back an operation result at the same time an other worker wants to read an incoming request. It results in two worker threads polling (one in read, one in write). nspr IO is not multi-threaded safe and those threads need to be synchronize.
all versions
So far no clear reproducer.
One thread can read 'fd' field that are modified under itself by the other thread. It can crash.
Should not crash
Metadata Update from @tbordaz: - Custom field origin adjusted to RHCust - Custom field reviewstatus adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1702740
Metadata Update from @tbordaz: - Issue assigned to tbordaz
PR https://pagure.io/389-ds-base/pull-request/50394
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.9
1b3c075..5f40c02 389-ds-base-1.3.9 -> 389-ds-base-1.3.9
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3447
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.