Displaying 8 results from an estimated 8 matches for "_submit_bh".
2018 Dec 12
5
CentOS 7.6 external USB dmesg issue
...fffa9746cae>] blk_queue_bio+0xfe/0x400
[ 1085.193772] [<ffffffffa9744ef7>] generic_make_request+0x147/0x380
[ 1085.193778] [<ffffffffa97451a0>] submit_bio+0x70/0x150
[ 1085.193786] [<ffffffffa967e555>] ? bio_alloc_bioset+0x115/0x310
[ 1085.193791] [<ffffffffa967a197>] _submit_bh+0x127/0x160
[ 1085.193797] [<ffffffffa967a1e0>] submit_bh+0x10/0x20
[ 1085.193808] [<ffffffffc1bd8424>]
ext4_read_block_bitmap_nowait+0x4c4/0x640 [ext4]
[ 1085.193828] [<ffffffffc1c16641>] ext4_mb_init_cache+0x181/0x6e0 [ext4]
[ 1085.193834] [<ffffffffa95c5afe>] ? lru_ca...
2013 Dec 17
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...00000000045eb56>] virtblk_request+0x25a/0x2b8
[<00000000003e749c>] __blk_run_queue+0x50/0x64
[<00000000003edb54>] blk_queue_bio+0x358/0x3f0
[<00000000003eb446>] generic_make_request+0xea/0x130
[<00000000003eb536>] submit_bio+0xaa/0x1a8
[<00000000002c95e8>] _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...
2013 Dec 17
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...00000000045eb56>] virtblk_request+0x25a/0x2b8
[<00000000003e749c>] __blk_run_queue+0x50/0x64
[<00000000003edb54>] blk_queue_bio+0x358/0x3f0
[<00000000003eb446>] generic_make_request+0xea/0x130
[<00000000003eb536>] submit_bio+0xaa/0x1a8
[<00000000002c95e8>] _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...
2013 Dec 23
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...gt;> [<00000000003e749c>] __blk_run_queue+0x50/0x64
>> [<00000000003edb54>] blk_queue_bio+0x358/0x3f0
>> [<00000000003eb446>] generic_make_request+0xea/0x130
>> [<00000000003eb536>] submit_bio+0xaa/0x1a8
>> [<00000000002c95e8>] _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/0x...
2013 Dec 23
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...gt;> [<00000000003e749c>] __blk_run_queue+0x50/0x64
>> [<00000000003edb54>] blk_queue_bio+0x358/0x3f0
>> [<00000000003eb446>] generic_make_request+0xea/0x130
>> [<00000000003eb536>] submit_bio+0xaa/0x1a8
>> [<00000000002c95e8>] _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/0x...
2013 Dec 19
0
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...blk_request+0x25a/0x2b8
> [<00000000003e749c>] __blk_run_queue+0x50/0x64
> [<00000000003edb54>] blk_queue_bio+0x358/0x3f0
> [<00000000003eb446>] generic_make_request+0xea/0x130
> [<00000000003eb536>] submit_bio+0xaa/0x1a8
> [<00000000002c95e8>] _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
> [<0000...
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