5 fvXddlZddlZddlZddlZddlZddlZddlZGddeZdZ y)Nc0eZdZdZdZddZdZdZdZy) PipeMutexzMutex using a pipe. Works across both greenlets and real threads, even at the same time. Class code copied from Swift's swift/common/utils.py Related eventlet bug: https://github.com/eventlet/eventlet/issues/432 ctj\|_|_t j|jtj }t j|jtj |tjztj|jdd|_ d|_ tjjdy)N-rF)ospiperfdwfdfcntlF_GETFLF_SETFL O_NONBLOCKwriteownerrecursion_deptheventletdebughub_prevent_multiple_readers)selfrflagss 5/usr/lib/python3/dist-packages/oslo_log/pipe_mutex.py__init__zPipeMutex.__init__"sWWY$(TXXu}}5 DHHemmVbmm-CD 4    33E:cttjj}|j|k(r|xj dz c_y t j|jd||_y#t$rZ}|jtjk7r|sYd}~ytjj|jdYd}~nd}~wwxYw)axAcquire the mutex. If called with blocking=False, returns True if the mutex was acquired and False if it wasn't. Otherwise, blocks until the mutex is acquired and returns True. This lock is recursive; the same greenthread may acquire it as many times as it wants to, though it must then release it that many times too. TNF)read)idr greenthread getcurrentrrrrr OSErrorerrnoEAGAINhubs trampoline)rblockingcurrent_greenthread_iderrs racquirezPipeMutex.acquire>s"$H$8$8$C$C$E!F ::/ /  A %  >!$3  >99 ,  (((== >s'A77 C C%+CCcttjj}|j|k7r t d|j dkDr|xj dzc_yd|_tj|jdy)zRelease the mutex.zcannot release un-acquired lockrrNX) rrrrr RuntimeErrorrrrr )rr&s rreleasezPipeMutex.releaseasp!#H$8$8$C$C$E!F ::/ /@A A   ! #  A %   4 rc|j&tj|jd|_|j&tj|jd|_d|_d|_y)z|Close the mutex. This releases its file descriptors. You can't use a mutex after it's been closed. Nr)r rcloser rrrs rr.zPipeMutex.closensU 88  HHTXX DH 88  HHTXX DH  rc$|jy)N)r.r/s r__del__zPipeMutex.__del__}s  rN)T) __name__ __module__ __qualname____doc__rr(r,r.r1rrrrs!;8!>F ! ! rrc"t|_y)z2Replacement for logging.Handler.createLock method.N)rlockr/s rpipe_createLockr9s  DIr) r!r rreventlet.debugeventlet.greenthread eventlet.hubsobjectrr9r6rrr>s0  oodr