Comment 1 for bug 722925

This bug seems a bit randomish. I tried to reproduce it the same way I did the first time and could not. A while later it happened when I run dmraid -an. I've hit it by doing several things, all of which seem to involve removing a dm device. I wrote down the call stack on one:

bdput
free_dev
__dm_destroy
dev_remove
ctl_ioctl
dm_ioctl