xapi-project / sm

35%

master: 47%

LAST BUILD ON BRANCH v2.11.0

branch: v2.11.0

CHANGE BRANCH

x

Reset

• v2.11.0
• master
• v1.10.0
• v1.11.1
• v1.11.2
• v1.11.3
• v1.13.0
• v1.14.0
• v1.14.1
• v1.16.1
• CA-240718
• CP-24279
• CA-263084
• cp-24893
• CA-255945
• CA-264210
• CA-267032
• CP-24548
• CA-257740
• pre-1.18
• v1.18.0
• CA-270011
• CA-276601
• CA-274584
• CA-267460
• CA-277346
• update-ut-dependencies
• CA-273731
• v1.20.0
• pre-1.19.0
• v1.19.0
• pre_1.20.0
• v1.21.0
• CA-292103
• v1.22.0
• v1.23.0
• v1.24.0
• feature/req488/master
• v1.25.0
• CA-247723
• v1.26.0
• v1.27.0
• v1.28.0
• v1.29.0
• feature/REQ-562/master
• v1.30.0
• v1.31.0
• team/ring0/linux-upstream
• v1.32.0
• feature/REQ-718
• v1.33.0
• v1.34.0
• v1.35.0
• v1.36.0
• v1.37.0
• v2.0.0
• v2.1.0
• v2.2.0
• release/naples/lcm
• v2.2.1
• v2.3.0
• v2.2.2
• v2.4.0
• v2.5.0
• v2.2.3
• v2.6.0
• marksy/CA-315152
• v2.7.0
• v2.8.0
• v2.9.0
• v2.10.0
• v2.12.0
• v2.13.0
• v2.14.0
• v2.15.0
• v2.16.0
• release/quebec/lcm
• private/bensi/CA-329841
• private/bensi/CA-329845
• v2.16.1
• v2.17.0
• private/bensi/CP-32204
• private/bensi/CA-331453
• v2.18.0
• private/bensi/CA-332806
• v2.19.0
• private/bensi/XSI_570
• v2.20.0
• v2.21.0
• private/bensi/CP-31856
• private/bensi/CA-335178
• feature/nbd
• private/bensi/CA-335721
• v2.22.0
• v2.23.0
• v2.24.0
• v2.25.0
• private/bensi/XSI-654
• v2.26.0
• v2.27.0
• private/bensi/CP-33629
• v2.28.0
• v2.29.0
• v2.30.0
• private/bensi/CP-32988
• v2.31.0
• v2.32.0
• v2.33.0
• v2.34.0
• v2.35.0
• v2.36.0
• v2.37.0
• v2.38.0
• v2.39.0
• v2.29.1
• v2.40.0
• private/bensi/XSI-915
• private/bensi/pathRefreshFix

Build # 796

Build Type

push

travis-ci

Committed by MarkSymsCtx

Commit Message

CA-323702: fcntl locks are per process, so need to reference count.

As fcntl locks are per-process it is not an error if a lock is acquired
that is already held, however the release is not reference counted by
the system. So, if a lock is taken by an API and subsequently another
method in the call chain takes the same lock it must not be released
until the API call completes.

To ensure this behaviour make Lock objects unique by name and namespace
so that subsequent calls obtain the same object reference. internally
to the object track how many calls to acquire and release have been made
and only release the underlying lock when all the acquires have had matching
release calls.

Signed-off-by: Mark Syms <mark.syms@citrix.com>

Run Details

866 of 6214 branches covered (13.94%)

7323 of 20739 relevant lines covered (35.31%)

0.35 hits per line