On Sat, Apr 25 2015 at 5:23am -0400,
Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
> Running dm-mpath against a tcm_loop target with two ALUA paths makes
> the kernel very unhappy when CONFIG_DM_MQ_DEFAULT is set. Without it
> it's perfectly happy.
Wonder if commit 63a4f065ec ("dm: fix add_disk() NULL pointer due to
race with free_dev()") left something not quite right relative to
blk-mq? Or maybe this is a problem confined to blk-mq itself.
What were you actually testing when this happened? Were you failing
paths under IO load or something?
Also, which upstream commit was your tree based on? Did you have any
non-upstream patches applied that I should be aware of?
Thanks,
Mike
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
