search for: 1e203650

...CPU: 0 COMMAND: "kworker/u128:1" #0 [1e2033e0] __schedule at 695ff2 #1 [1e203530] log_wait_commit at 3a28a6 #2 [1e2035a0] ext3_sync_fs at 328dea #3 [1e2035d8] sync_filesystem at 2c785c #4 [1e203600] fsync_bdev at 2d4650 #5 [1e203628] invalidate_partition at 3f80c8 #6 [1e203650] del_gendisk at 3f8f5c #7 [1e2036c8] virtblk_remove at 45e60e #8 [1e203700] virtio_dev_remove at 42d72e #9 [1e203738] __device_release_driver at 44f0b0 #10 [1e203760] device_release_driver at 44f16c #11 [1e203788] bus_remove_device at 44ea92 #12 [1e2037b8] device_del at 44bb40 #13 [1e2037f0]...

...CPU: 0 COMMAND: "kworker/u128:1" #0 [1e2033e0] __schedule at 695ff2 #1 [1e203530] log_wait_commit at 3a28a6 #2 [1e2035a0] ext3_sync_fs at 328dea #3 [1e2035d8] sync_filesystem at 2c785c #4 [1e203600] fsync_bdev at 2d4650 #5 [1e203628] invalidate_partition at 3f80c8 #6 [1e203650] del_gendisk at 3f8f5c #7 [1e2036c8] virtblk_remove at 45e60e #8 [1e203700] virtio_dev_remove at 42d72e #9 [1e203738] __device_release_driver at 44f0b0 #10 [1e203760] device_release_driver at 44f16c #11 [1e203788] bus_remove_device at 44ea92 #12 [1e2037b8] device_del at 44bb40 #13 [1e2037f0]...

...33e0] __schedule at 695ff2 >> #1 [1e203530] log_wait_commit at 3a28a6 >> #2 [1e2035a0] ext3_sync_fs at 328dea >> #3 [1e2035d8] sync_filesystem at 2c785c >> #4 [1e203600] fsync_bdev at 2d4650 >> #5 [1e203628] invalidate_partition at 3f80c8 >> #6 [1e203650] del_gendisk at 3f8f5c >> #7 [1e2036c8] virtblk_remove at 45e60e >> #8 [1e203700] virtio_dev_remove at 42d72e >> #9 [1e203738] __device_release_driver at 44f0b0 >> #10 [1e203760] device_release_driver at 44f16c >> #11 [1e203788] bus_remove_device at 44ea92 &gt...

...33e0] __schedule at 695ff2 >> #1 [1e203530] log_wait_commit at 3a28a6 >> #2 [1e2035a0] ext3_sync_fs at 328dea >> #3 [1e2035d8] sync_filesystem at 2c785c >> #4 [1e203600] fsync_bdev at 2d4650 >> #5 [1e203628] invalidate_partition at 3f80c8 >> #6 [1e203650] del_gendisk at 3f8f5c >> #7 [1e2036c8] virtblk_remove at 45e60e >> #8 [1e203700] virtio_dev_remove at 42d72e >> #9 [1e203738] __device_release_driver at 44f0b0 >> #10 [1e203760] device_release_driver at 44f16c >> #11 [1e203788] bus_remove_device at 44ea92 &gt...

...r/u128:1" > #0 [1e2033e0] __schedule at 695ff2 > #1 [1e203530] log_wait_commit at 3a28a6 > #2 [1e2035a0] ext3_sync_fs at 328dea > #3 [1e2035d8] sync_filesystem at 2c785c > #4 [1e203600] fsync_bdev at 2d4650 > #5 [1e203628] invalidate_partition at 3f80c8 > #6 [1e203650] del_gendisk at 3f8f5c > #7 [1e2036c8] virtblk_remove at 45e60e > #8 [1e203700] virtio_dev_remove at 42d72e > #9 [1e203738] __device_release_driver at 44f0b0 > #10 [1e203760] device_release_driver at 44f16c > #11 [1e203788] bus_remove_device at 44ea92 > #12 [1e2037b8] device...

Hi, here is my v4 patch-set update to the v3 RFC submitted on Nov 27th. When an active virtio block device is hot-unplugged from a KVM guest, affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in appropriate error info. Additionally a potential

Hi, here is my v4 patch-set update to the v3 RFC submitted on Nov 27th. When an active virtio block device is hot-unplugged from a KVM guest, affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in appropriate error info. Additionally a potential