LTTng bugs repository

01/30/2017

10:02 PM Userspace RCU Bug #991: Memory leak after call_rcu

Ok, you have convinced me. Thank you for your time and effort! You can close the issue. Daniel Salzman

04:15 PM Userspace RCU Bug #991: Memory leak after call_rcu

Yes, that sound good.
Thank you! Daniel Salzman

02:20 PM Userspace RCU Bug #991: Memory leak after call_rcu

The reason why we don't like this leak is our automated testing, which is based on Valgrind and would need some worka... Daniel Salzman

02:10 PM Userspace RCU Bug #991: Memory leak after call_rcu

I understand this argument.
It is important to say that invoking of "rcu_cleanup" is optional. Just a hint for the... Daniel Salzman

01:18 PM Userspace RCU Bug #991: Memory leak after call_rcu

If rcu_cleanup could block until the queue is not empty, then we would be happy :-) Daniel Salzman

12/01/2016

08:04 AM Userspace RCU Bug #991: Memory leak after call_rcu

Hi Mathieu,
What about adding something like "rcu_cleanup" which, if called, will free the call_rcu queue explicitly? Daniel Salzman

01/22/2016

03:56 AM Userspace RCU Bug #991 (Resolved): Memory leak after call_rcu

The problem also applies to the latest 0.9.1 source. Attached a valgrind summary
for doc/examples/urcu-flavors/mb.c
... Daniel Salzman