Re: refcounts assertion

2016-03-07 Thread Samuel Thibault
Justus Winter, on Mon 07 Mar 2016 11:40:26 +0100, wrote: > I have a patch that revamps it so that we avoid the copying. How would it look like? Does that mean that the fun would be called with the htable lock held? > The thing with the patch is (iirc) that it requires the called > function to be

Re: refcounts assertion

2016-03-07 Thread Justus Winter
Quoting Samuel Thibault (2016-03-07 01:40:01) > Hello, > > Some kind of refcount assertion failure we have been having is "refcount > detected use-after-free!" from the call to refcounts_ref inside > _ports_bucket_class_iterate, called for instance by the periodic sync. > I'm thinking: what about

refcounts assertion

2016-03-06 Thread Samuel Thibault
Hello, Some kind of refcount assertion failure we have been having is "refcount detected use-after-free!" from the call to refcounts_ref inside _ports_bucket_class_iterate, called for instance by the periodic sync. I'm thinking: what about this scenario: - thread A calls diskfs_nput() - that call