Hi,
Is the scenario possible?
There is an doing op X and its OBC info is stored in the container:
SharedLRU<>::object_contexts;
In the meantime,
there are many other OPs comming, and cause "lru_remove" the OBC of op X.
If there is a new op trying to access the same object as op X, it
may get something wrong.
Yufan Chen
--
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
