On Thu, 2017-03-16 at 23:00 +0000, Bart Van Assche wrote: > The following crash only occurs with async aborts enabled: > > general protection fault: 0000 [#1] SMP > RIP: 0010:scsi_device_put+0xb/0x30 > Call Trace: > scsi_disk_put+0x2d/0x40 > sd_release+0x3d/0xb0 > __blkdev_put+0x29e/0x360 > blkdev_put+0x49/0x170 > dm_put_table_device+0x58/0xc0 [dm_mod] > dm_put_device+0x70/0xc0 [dm_mod] > free_priority_group+0x92/0xc0 [dm_multipath] > free_multipath+0x70/0xc0 [dm_multipath] > multipath_dtr+0x19/0x20 [dm_multipath] > dm_table_destroy+0x67/0x120 [dm_mod] > dev_suspend+0xde/0x240 [dm_mod] > ctl_ioctl+0x1f5/0x520 [dm_mod] > dm_ctl_ioctl+0xe/0x20 [dm_mod] > do_vfs_ioctl+0x8f/0x700 > SyS_ioctl+0x3c/0x70 > entry_SYSCALL_64_fastpath+0x18/0xad
(replying to my own e-mail) With my three scsi_dh_alua patches applied I don't see this crash anymore so this crash was probably unrelated to async aborts. Bart.
