On 09/24/2015 05:42 PM, Junichi Nomura wrote:
Since __dm_destroy() depends on monotonic decrease of md->holders,
assertion check of !DMF_FREEING in dm_get() is a valid protection
from use-after-free. If we are to remove the check, __dm_destroy()
should be changed to cope with the situation.
I'm curious why there were pending I/Os after DMF_FEEING set.
Can this problem be reproducible with non dm-mq setup or older kernels?
How did you remove the dm device in your testing?
Hello Junichi,
Thanks for stepping in.
Sorry but I do not know whether or not this problem is reproducible
without dm-mq or with older kernels.
The dm device was removed via the command "dmsetup remove_all".
Bart.
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
