search for: 6b0a5e

...4d3cea #36 [163f7c10] bus_for_each_dev at 45ea56 #37 [163f7c50] for_each_subchannel_staged at 4d337e #38 [163f7c98] css_slow_path_func at 4d3450 #39 [163f7cc0] process_one_work at 164ff4 #40 [163f7d60] worker_thread at 166500 #41 [163f7da8] kthread at 16e67c #42 [163f7eb0] kernel_thread_starter at 6b0a5e Removing a disk while writing to it now ends up mostly with errors (which is new behavior and good). However, the detached device is still listed under /dev, and a subsequent umount ends up in a hang. Latter also occurred with my approach, sometimes. Sometimes everything ends up in QEMU crashes,...

...4d3cea #36 [163f7c10] bus_for_each_dev at 45ea56 #37 [163f7c50] for_each_subchannel_staged at 4d337e #38 [163f7c98] css_slow_path_func at 4d3450 #39 [163f7cc0] process_one_work at 164ff4 #40 [163f7d60] worker_thread at 166500 #41 [163f7da8] kthread at 16e67c #42 [163f7eb0] kernel_thread_starter at 6b0a5e Removing a disk while writing to it now ends up mostly with errors (which is new behavior and good). However, the detached device is still listed under /dev, and a subsequent umount ends up in a hang. Latter also occurred with my approach, sometimes. Sometimes everything ends up in QEMU crashes,...

..._each_dev at 45ea56 > #37 [163f7c50] for_each_subchannel_staged at 4d337e > #38 [163f7c98] css_slow_path_func at 4d3450 > #39 [163f7cc0] process_one_work at 164ff4 > #40 [163f7d60] worker_thread at 166500 > #41 [163f7da8] kthread at 16e67c > #42 [163f7eb0] kernel_thread_starter at 6b0a5e > > Removing a disk while writing to it now ends up mostly > with errors (which is new behavior and good). > However, the detached device is still listed under /dev, and a > subsequent umount ends up in a hang. Latter also occurred with > my approach, sometimes. > > Sometim...

...> #37 [163f7c50] for_each_subchannel_staged at 4d337e >> #38 [163f7c98] css_slow_path_func at 4d3450 >> #39 [163f7cc0] process_one_work at 164ff4 >> #40 [163f7d60] worker_thread at 166500 >> #41 [163f7da8] kthread at 16e67c >> #42 [163f7eb0] kernel_thread_starter at 6b0a5e >> >> Removing a disk while writing to it now ends up mostly >> with errors (which is new behavior and good). >> However, the detached device is still listed under /dev, and a >> subsequent umount ends up in a hang. Latter also occurred with >> my approach, somet...

...> #37 [163f7c50] for_each_subchannel_staged at 4d337e >> #38 [163f7c98] css_slow_path_func at 4d3450 >> #39 [163f7cc0] process_one_work at 164ff4 >> #40 [163f7d60] worker_thread at 166500 >> #41 [163f7da8] kthread at 16e67c >> #42 [163f7eb0] kernel_thread_starter at 6b0a5e >> >> Removing a disk while writing to it now ends up mostly >> with errors (which is new behavior and good). >> However, the detached device is still listed under /dev, and a >> subsequent umount ends up in a hang. Latter also occurred with >> my approach, somet...

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