You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@celix.apache.org by "Bjoern Petri (JIRA)" <ji...@apache.org> on 2014/09/01 22:30:20 UTC

[jira] [Created] (CELIX-147) RSA_SHM: concurrency issue when client segfaults

Bjoern Petri created CELIX-147:
----------------------------------

             Summary: RSA_SHM: concurrency issue when client segfaults
                 Key: CELIX-147
                 URL: https://issues.apache.org/jira/browse/CELIX-147
             Project: Celix
          Issue Type: Bug
            Reporter: Bjoern Petri
            Assignee: Bjoern Petri


Assuming a RSA_SHM client segfaults after it has put a request in the shared memory block, a signal handler could still call the remoteServiceAdmin_stop function which will unlock the semaphore (0) for the critical area again. If the RSA_SHM server puts it reply afterwards in the shared memory block, it can leave the sync semaphores (1,2) in an unwanted state which could block all following RSA_SHM communication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)