On 12/08/2019 13:49, Mateusz Guzik wrote:
> On 8/12/19, Andriy Gapon wrote:
>>
>> I am trying to debug a leak of a shared vnode lock and I noticed that
>> there is no check for td_lk_slocks in userret. There are checks for
>> td_rw_rlocks and td_sx_slocks. I wonder if there is any valid
On Mon, Aug 12, 2019 at 12:14:25PM +0300, Andriy Gapon wrote:
>
> I am trying to debug a leak of a shared vnode lock and I noticed that
> there is no check for td_lk_slocks in userret. There are checks for
> td_rw_rlocks and td_sx_slocks. I wonder if there is any valid scenario
> where a thread
On 8/12/19, Andriy Gapon wrote:
>
> I am trying to debug a leak of a shared vnode lock and I noticed that
> there is no check for td_lk_slocks in userret. There are checks for
> td_rw_rlocks and td_sx_slocks. I wonder if there is any valid scenario
> where a thread is allowed to retain a shared
I am trying to debug a leak of a shared vnode lock and I noticed that
there is no check for td_lk_slocks in userret. There are checks for
td_rw_rlocks and td_sx_slocks. I wonder if there is any valid scenario
where a thread is allowed to retain a shared lock manager lock across
system calls.