librados: don't use lockdep for AioCompletionImpl

This is a quick workaround for the next branch. A more complete fix
will be done for the master branch. This does not affect correctness,
just what qa runs with lockdep enabled do.

Signed-off-by: Josh Durgin <josh.durgin@inktank.com>
Reviewed-by: Sage Weil <sage.weil@inktank.com>
(cherry picked from commit 267ce0d90b8f3afaaddfdc0556c9bafbf4628426)

diff --git a/src/librados/AioCompletionImpl.h b/src/librados/AioCompletionImpl.h
index 619e7471605d4218fe9800dcfdbf505447a7c663..b3e1e8a16e2c5f08814388e48fe2bd175abf4fc4 100644 (file)
--- a/src/librados/AioCompletionImpl.h
+++ b/src/librados/AioCompletionImpl.h
@@ -47,7 +47,7 @@ struct librados::AioCompletionImpl {
   tid_t aio_write_seq;
   xlist<AioCompletionImpl*>::item aio_write_list_item;
 
-  AioCompletionImpl() : lock("AioCompletionImpl lock"),
+  AioCompletionImpl() : lock("AioCompletionImpl lock", false, false),
                        ref(1), rval(0), released(false), ack(false), safe(false),
                        callback_complete(0), callback_safe(0), callback_arg(0),
                        is_read(false), pbl(0), buf(0), maxlen(0),