On Fri, 23 Mar 2018, Mikulas Patocka wrote: > This test isn't locked against anything, so it may race with concurrent > allocation. "any_slab_objects" may return false and a new object in the > slab cache may appear immediatelly after that. Ok the same reasoning applies to numerous other slab configuration settings in /sys/kernel/slab.... So we need to disable all of that or come up with a sane way of synchronization. -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
