Displaying 7 results from an estimated 7 matches for "163f7460".
Did you mean:
163f72e0
2014 Jan 28
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...ome testing...
Removing a disk while reading from it mostly still ends up
in hangs as of below:
PID: 13 TASK: 163f8000 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 [163f7...
2014 Jan 28
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...ome testing...
Removing a disk while reading from it mostly still ends up
in hangs as of below:
PID: 13 TASK: 163f8000 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 [163f7...
2014 Jan 29
0
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...39;t Happen (often).
At this point, I ask Jens :)
Cheers,
Rusty.
>
> PID: 13 TASK: 163f8000 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] de...
2014 Feb 18
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...ue() that
> Cheers,
> Rusty.
>
>>
>> PID: 13 TASK: 163f8000 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 407ba...
2014 Feb 18
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...ue() that
> Cheers,
> Rusty.
>
>>
>> PID: 13 TASK: 163f8000 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 407ba...
2013 Dec 13
7
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_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
2013 Dec 13
7
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_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