Displaying 7 results from an estimated 7 matches for "1786fc".
Did you mean:
1786
2013 Dec 17
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...5e8>] _submit_bh+0x1c4/0x2f4
[<00000000003a25e4>] journal_write_superblock+0xa0/0x1fc
[<00000000003a3ed4>] journal_update_sb_log_tail+0x48/0x7c
[<000000000039e742>] journal_commit_transaction+0x1586/0x1aa0
[<00000000003a2a0e>] kjournald+0xfe/0x2a0
[<00000000001786fc>] kthread+0xd8/0xe0
[<0000000000698fee>] kernel_thread_starter+0x6/0xc
2 locks held by kjournald/1984:
... and end up in hang situations ...
PID: 13 TASK: 1e3f8000 CPU: 0 COMMAND: "kworker/u128:1"
#0 [1e2033e0] __schedule at 695ff2
#1 [1e203530] log_wait_co...
2013 Dec 17
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...5e8>] _submit_bh+0x1c4/0x2f4
[<00000000003a25e4>] journal_write_superblock+0xa0/0x1fc
[<00000000003a3ed4>] journal_update_sb_log_tail+0x48/0x7c
[<000000000039e742>] journal_commit_transaction+0x1586/0x1aa0
[<00000000003a2a0e>] kjournald+0xfe/0x2a0
[<00000000001786fc>] kthread+0xd8/0xe0
[<0000000000698fee>] kernel_thread_starter+0x6/0xc
2 locks held by kjournald/1984:
... and end up in hang situations ...
PID: 13 TASK: 1e3f8000 CPU: 0 COMMAND: "kworker/u128:1"
#0 [1e2033e0] __schedule at 695ff2
#1 [1e203530] log_wait_co...
2013 Dec 23
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...0000000003a25e4>] journal_write_superblock+0xa0/0x1fc
>> [<00000000003a3ed4>] journal_update_sb_log_tail+0x48/0x7c
>> [<000000000039e742>] journal_commit_transaction+0x1586/0x1aa0
>> [<00000000003a2a0e>] kjournald+0xfe/0x2a0
>> [<00000000001786fc>] kthread+0xd8/0xe0
>> [<0000000000698fee>] kernel_thread_starter+0x6/0xc
>> 2 locks held by kjournald/1984:
>>
>> ... and end up in hang situations ...
>>
>> PID: 13 TASK: 1e3f8000 CPU: 0 COMMAND: "kworker/u128:1"
>>...
2013 Dec 23
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...0000000003a25e4>] journal_write_superblock+0xa0/0x1fc
>> [<00000000003a3ed4>] journal_update_sb_log_tail+0x48/0x7c
>> [<000000000039e742>] journal_commit_transaction+0x1586/0x1aa0
>> [<00000000003a2a0e>] kjournald+0xfe/0x2a0
>> [<00000000001786fc>] kthread+0xd8/0xe0
>> [<0000000000698fee>] kernel_thread_starter+0x6/0xc
>> 2 locks held by kjournald/1984:
>>
>> ... and end up in hang situations ...
>>
>> PID: 13 TASK: 1e3f8000 CPU: 0 COMMAND: "kworker/u128:1"
>>...
2013 Dec 19
0
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
.../0x2f4
> [<00000000003a25e4>] journal_write_superblock+0xa0/0x1fc
> [<00000000003a3ed4>] journal_update_sb_log_tail+0x48/0x7c
> [<000000000039e742>] journal_commit_transaction+0x1586/0x1aa0
> [<00000000003a2a0e>] kjournald+0xfe/0x2a0
> [<00000000001786fc>] kthread+0xd8/0xe0
> [<0000000000698fee>] kernel_thread_starter+0x6/0xc
> 2 locks held by kjournald/1984:
>
> ... and end up in hang situations ...
>
> PID: 13 TASK: 1e3f8000 CPU: 0 COMMAND: "kworker/u128:1"
> #0 [1e2033e0] __schedule at 6...
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