search for: 22d0a6

...8000 CPU: 0 COMMAND: "kworker/u128:1" #0 [163f72e0] __schedule at 6aa22c #1 [163f7428] io_schedule at 6aab6c #2 [163f7448] sleep_on_page at 22cbb2 #3 [163f7460] __wait_on_bit at 6ab394 #4 [163f74b0] wait_on_page_bit at 22cef4 #5 [163f7508] filemap_fdatawait_range at 22d0a6 #6 [163f75e8] filemap_write_and_wait at 22de62 #7 [163f7618] fsync_bdev at 2dc5d8 #8 [163f7640] invalidate_partition at 407ba8 #9 [163f7668] del_gendisk at 408a4c #10 [163f76c0] virtblk_remove at 46f81e #11 [163f76f8] virtio_dev_remove at 43d302 #12 [163f7730] __device_release_driver at 460...

...8000 CPU: 0 COMMAND: "kworker/u128:1" #0 [163f72e0] __schedule at 6aa22c #1 [163f7428] io_schedule at 6aab6c #2 [163f7448] sleep_on_page at 22cbb2 #3 [163f7460] __wait_on_bit at 6ab394 #4 [163f74b0] wait_on_page_bit at 22cef4 #5 [163f7508] filemap_fdatawait_range at 22d0a6 #6 [163f75e8] filemap_write_and_wait at 22de62 #7 [163f7618] fsync_bdev at 2dc5d8 #8 [163f7640] invalidate_partition at 407ba8 #9 [163f7668] del_gendisk at 408a4c #10 [163f76c0] virtblk_remove at 46f81e #11 [163f76f8] virtio_dev_remove at 43d302 #12 [163f7730] __device_release_driver at 460...

...: "kworker/u128:1" > #0 [163f72e0] __schedule at 6aa22c > #1 [163f7428] io_schedule at 6aab6c > #2 [163f7448] sleep_on_page at 22cbb2 > #3 [163f7460] __wait_on_bit at 6ab394 > #4 [163f74b0] wait_on_page_bit at 22cef4 > #5 [163f7508] filemap_fdatawait_range at 22d0a6 > #6 [163f75e8] filemap_write_and_wait at 22de62 > #7 [163f7618] fsync_bdev at 2dc5d8 > #8 [163f7640] invalidate_partition at 407ba8 > #9 [163f7668] del_gendisk at 408a4c > #10 [163f76c0] virtblk_remove at 46f81e > #11 [163f76f8] virtio_dev_remove at 43d302 > #12 [163f7...

...gt;> #0 [163f72e0] __schedule at 6aa22c >> #1 [163f7428] io_schedule at 6aab6c >> #2 [163f7448] sleep_on_page at 22cbb2 >> #3 [163f7460] __wait_on_bit at 6ab394 >> #4 [163f74b0] wait_on_page_bit at 22cef4 >> #5 [163f7508] filemap_fdatawait_range at 22d0a6 >> #6 [163f75e8] filemap_write_and_wait at 22de62 >> #7 [163f7618] fsync_bdev at 2dc5d8 >> #8 [163f7640] invalidate_partition at 407ba8 >> #9 [163f7668] del_gendisk at 408a4c >> #10 [163f76c0] virtblk_remove at 46f81e >> #11 [163f76f8] virtio_dev_remo...

...gt;> #0 [163f72e0] __schedule at 6aa22c >> #1 [163f7428] io_schedule at 6aab6c >> #2 [163f7448] sleep_on_page at 22cbb2 >> #3 [163f7460] __wait_on_bit at 6ab394 >> #4 [163f74b0] wait_on_page_bit at 22cef4 >> #5 [163f7508] filemap_fdatawait_range at 22d0a6 >> #6 [163f75e8] filemap_write_and_wait at 22de62 >> #7 [163f7618] fsync_bdev at 2dc5d8 >> #8 [163f7640] invalidate_partition at 407ba8 >> #9 [163f7668] del_gendisk at 408a4c >> #10 [163f76c0] virtblk_remove at 46f81e >> #11 [163f76f8] virtio_dev_remo...

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