Re: s/Mutex/ceph::mutex/, lockdep

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 13 Mar 2018, Sage Weil wrote:

I think one wrinkle is that we have lots of lines like

 assert(lock.is_locked_by_me());

...and very importantly, there is /no/ good way to actually detect this!

sprinkled about, usually at the top of internal _foo() methods.  I don't
think there is a std::mutex equivalent (that operates on the mutex itself
and not a std::unique_lock).

No accident-- at least if it's what I'm thinking of, there's no reliable way to do it. (I haven't looked at this in a few months, I may be confusing it with something else, but I'm pretty sure that's the case.)

-Jesse
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux