[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-52] fix deadlock in closing a channel closing a channel would enter an odd codepath where the lock was grabbed, some stuff was done, then another function was called where the lock was grabbed again.  unfortunately python locks aren't monitors so this would deadlock.  instead, make the smaller function lock-free with an explicit notice that you must be holding the lock before calling.
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-52]
fix deadlock in closing a channel
closing a channel would enter an odd codepath where the lock was grabbed,
some stuff was done, then another function was called where the lock was
grabbed again.  unfortunately python locks aren't monitors so this would
deadlock.  instead, make the smaller function lock-free with an explicit
notice that you must be holding the lock before calling.

mirrorcoder/paramiko,dorianpula/paramiko,davidbistolas/paramiko,paramiko/paramiko,varunarya10/paramiko,ameily/paramiko,dlitz/paramiko,anadigi/paramiko,thisch/paramiko,esc/paramiko,Bluehorn/paramiko,jaraco/paramiko,thusoy/paramiko,zpzgone/paramiko,bitprophet/ssh,fvicente/paramiko,mitsuhiko/paramiko,Automatic/paramiko,toby82/paramiko,alex/paramiko,selboo/paramiko,jorik041/paramiko,SebastianDeiss/paramiko,rcorrieri/paramiko,torkil/paramiko,zarr12steven/paramiko,remram44/paramiko,reaperhulk/paramiko,digitalquacks/paramiko,CptLemming/paramiko,mhdaimi/paramiko,nischu7/paramiko,redixin/paramiko