#50489 With Nunc-stans, connection_table_get_connection looks not thread safe to multiple new connection handler
Closed: wontfix by mreynolds. Opened by tbordaz.

Issue Description

This ticket is opened as a followup of a review (https://pagure.io/389-ds-base/pull-request/50485#comment-91245)

WIth NS, the server registers multiple new connection handlers that can run in parallel.
The function connection_table_get_connection looks not thread safe to concurrent access.

Package Version and Platform

Since 1.3.6 and introduction of NS

Steps to reproduce

N/A

So far no failure has been detected in connection_table_get_connection.
But if this function is not thread safe it is a potential source of sigsev or weird behavior

Actual results

connection_table_get_connection is potentially not thread safe

Expected results

connection_table_get_connection should be thread safe in context of several new connection handler


This ticket is handled with PR https://pagure.io/389-ds-base/pull-request/50492#

Metadata Update from @tbordaz:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

Metadata Update from @mreynolds:
- Issue close_status updated to: duplicate
- Issue set to the milestone: 1.4.1
- Issue status updated to: Closed (was: Open)

Fixed with https://pagure.io/389-ds-base/issue/50459#comment-581685 merge

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/3546

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: duplicate)

Metadata