possible race condition deadlock

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/4086

• Created at 2019-09-24 11:10:48 by pbrezina
• Assigned to nobody

---

To reproduce, apply the following patch and run integration tests:

diff --git a/src/providers/ldap/sdap_sudo_shared.c b/src/providers/ldap/sdap_sudo_shared.c
index 6619b0136..679ec16a6 100644
--- a/src/providers/ldap/sdap_sudo_shared.c
+++ b/src/providers/ldap/sdap_sudo_shared.c
@@ -184,6 +184,8 @@ sdap_sudo_set_usn(struct sdap_server_opts *srv_opts,
         return;
     }
 
+    strcmp(srv_opts->max_sudo_value, "0");
+
     errno = 0;
     usn_number = strtoul(usn, &endptr, 10);
     if (errno != 0) {

sssd_be process segfaulted in CI because srv_opts->max_sudo_value was NULL. This happened every time when the process was started. Then we hit a race condition where the new sssd_be process was trying to connect to the monitor but at the same time, the monitor was ordered to shutdown by CI test.

Comments

---

Comment from thalman at 2020-03-13 15:41:42

Metadata Update from @thalman:

• Issue tagged with: Future milestone

[andreboscatto]

Dear Contributor/User,

Recognizing the importance of addressing enhancements, bugs, and issues for the SSSD project's quality and reliability, we also need to consider our long-term goals and resource constraints.

After thoughtful consideration, regrettably, we are unable to address this request at this time. To avoid any misconception, we're closing it; however, we encourage continued collaboration and contributions from anyone interested.

We apologize for any inconvenience and appreciate your understanding of our resource limitations. While you're welcome to open a new issue (or reopen this one), immediate attention may not be guaranteed due to competing priorities.

Thank you once again for sharing your feedback. We look forward to ongoing collaboration to deliver the best possible solutions, supporting in any way we can.

Best regards,
André Boscatto