search for: block_ioctl

Displaying 19 results from an estimated 19 matches for "block_ioctl".

2020 Apr 30
2
[PATCH v3] virtio-blk: handle block_device_operations callbacks after hot unplug
...DR7: 0000000000000400 > > Call Trace: > > [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] > > [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 > > [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 > > [<ffffffff8d488771>] block_ioctl+0x41/0x50 > > [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 > > [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 > > > > A related problem is that virtblk_remove() leaks the vd_index_ida index > > when something still holds a reference to vblk->disk durin...
2020 Apr 30
2
[PATCH v3] virtio-blk: handle block_device_operations callbacks after hot unplug
...DR7: 0000000000000400 > > Call Trace: > > [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] > > [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 > > [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 > > [<ffffffff8d488771>] block_ioctl+0x41/0x50 > > [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 > > [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 > > > > A related problem is that virtblk_remove() leaks the vd_index_ida index > > when something still holds a reference to vblk->disk durin...
2012 Nov 15
1
virtio_blk BUG on detach-disk/attach-disk of mounted vd
...ac28680 ffff880118c6bee8 [ 75.115090] Call Trace: [ 75.115101] [<ffffffff813d0bfb>] ? virtblk_ioctl+0x4b/0x90 [ 75.115118] [<ffffffff812bd1be>] blkdev_ioctl+0xde/0x830 [ 75.115130] [<ffffffff8118b406>] ? cp_new_stat+0x116/0x130 [ 75.115140] [<ffffffff811bc940>] block_ioctl+0x40/0x50 [ 75.115146] [<ffffffff81197ac8>] do_vfs_ioctl+0x98/0x550 [ 75.115149] [<ffffffff81198011>] sys_ioctl+0x91/0xb0 [ 75.115162] [<ffffffff810db086>] ? __audit_syscall_exit+0x3d6/0x410 [ 75.115175] [<ffffffff81625519>] system_call_fastpath+0x16/0x1b [ 75....
2012 Nov 15
1
virtio_blk BUG on detach-disk/attach-disk of mounted vd
...ac28680 ffff880118c6bee8 [ 75.115090] Call Trace: [ 75.115101] [<ffffffff813d0bfb>] ? virtblk_ioctl+0x4b/0x90 [ 75.115118] [<ffffffff812bd1be>] blkdev_ioctl+0xde/0x830 [ 75.115130] [<ffffffff8118b406>] ? cp_new_stat+0x116/0x130 [ 75.115140] [<ffffffff811bc940>] block_ioctl+0x40/0x50 [ 75.115146] [<ffffffff81197ac8>] do_vfs_ioctl+0x98/0x550 [ 75.115149] [<ffffffff81198011>] sys_ioctl+0x91/0xb0 [ 75.115162] [<ffffffff810db086>] ? __audit_syscall_exit+0x3d6/0x410 [ 75.115175] [<ffffffff81625519>] system_call_fastpath+0x16/0x1b [ 75....
2020 Apr 30
3
[PATCH v4] virtio-blk: handle block_device_operations callbacks after hot unplug
...000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 [<ffffffff8d488771>] block_ioctl+0x41/0x50 [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 A related problem is that virtblk_remove() leaks the vd_index_ida index when something still holds a reference to vblk->disk during hot unplug. This causes virtio-blk device names...
2020 Apr 30
3
[PATCH v4] virtio-blk: handle block_device_operations callbacks after hot unplug
...000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 [<ffffffff8d488771>] block_ioctl+0x41/0x50 [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 A related problem is that virtblk_remove() leaks the vd_index_ida index when something still holds a reference to vblk->disk during hot unplug. This causes virtio-blk device names...
2020 Apr 29
2
[PATCH v3] virtio-blk: handle block_device_operations callbacks after hot unplug
...000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 [<ffffffff8d488771>] block_ioctl+0x41/0x50 [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 A related problem is that virtblk_remove() leaks the vd_index_ida index when something still holds a reference to vblk->disk during hot unplug. This causes virtio-blk device names...
2020 Apr 29
2
[PATCH v3] virtio-blk: handle block_device_operations callbacks after hot unplug
...000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 [<ffffffff8d488771>] block_ioctl+0x41/0x50 [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 A related problem is that virtblk_remove() leaks the vd_index_ida index when something still holds a reference to vblk->disk during hot unplug. This causes virtio-blk device names...
2006 Jan 06
2
3ware disk failure -> hang
I've got an i386 server running centos 4.2 with 3 3ware controllers in it -- an 8006-2 for the system disks and 2 7500-8s. On the 7500s, I'm running an all software RAID50. This morning I came in to find the system hung. Turns out a disk went overnight on one of the 7500s, and rather than a graceful failover I got this: Jan 6 01:03:58 $SERVER kernel: 3w-xxxx: scsi2: Command
2017 Sep 15
2
Regression in virtio block driver with 4.13.2
...[ 5.914588] Call Trace: [ 5.914599] sg_io+0xe2/0x400 [ 5.914611] ? __might_fault+0x85/0x90 [ 5.914622] scsi_cmd_ioctl+0x2e0/0x4a0 [ 5.914637] scsi_cmd_blk_ioctl+0x42/0x50 [ 5.914651] virtblk_ioctl+0x56/0x70 [virtio_blk] [ 5.914666] blkdev_ioctl+0x8f7/0x9b0 [ 5.914679] block_ioctl+0x43/0x50 [ 5.914689] do_vfs_ioctl+0xa6/0x6c0 [ 5.914702] SyS_ioctl+0x79/0x90 [ 5.914714] entry_SYSCALL_64_fastpath+0x1f/0xbe [ 5.914727] RIP: 0033:0x7f03e3b220d7 [ 5.914737] RSP: 002b:00007fff674992f8 EFLAGS: 00000202 ORIG_RAX: 0000000000000010 [ 5.914758] RAX: ffffffffffffff...
2017 Sep 15
2
Regression in virtio block driver with 4.13.2
...[ 5.914588] Call Trace: [ 5.914599] sg_io+0xe2/0x400 [ 5.914611] ? __might_fault+0x85/0x90 [ 5.914622] scsi_cmd_ioctl+0x2e0/0x4a0 [ 5.914637] scsi_cmd_blk_ioctl+0x42/0x50 [ 5.914651] virtblk_ioctl+0x56/0x70 [virtio_blk] [ 5.914666] blkdev_ioctl+0x8f7/0x9b0 [ 5.914679] block_ioctl+0x43/0x50 [ 5.914689] do_vfs_ioctl+0xa6/0x6c0 [ 5.914702] SyS_ioctl+0x79/0x90 [ 5.914714] entry_SYSCALL_64_fastpath+0x1f/0xbe [ 5.914727] RIP: 0033:0x7f03e3b220d7 [ 5.914737] RSP: 002b:00007fff674992f8 EFLAGS: 00000202 ORIG_RAX: 0000000000000010 [ 5.914758] RAX: ffffffffffffff...
2020 Apr 30
0
[PATCH v3] virtio-blk: handle block_device_operations callbacks after hot unplug
...; > > Call Trace: > > > [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] > > > [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 > > > [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 > > > [<ffffffff8d488771>] block_ioctl+0x41/0x50 > > > [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 > > > [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 > > > > > > A related problem is that virtblk_remove() leaks the vd_index_ida index > > > when something still holds a referen...
2020 May 04
0
[PATCH v4] virtio-blk: handle block_device_operations callbacks after hot unplug
...00 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > Call Trace: > [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] > [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 > [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 > [<ffffffff8d488771>] block_ioctl+0x41/0x50 > [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 > [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 > > A related problem is that virtblk_remove() leaks the vd_index_ida index > when something still holds a reference to vblk->disk during hot unplug. > This c...
2012 Oct 03
1
OCZ Vertex3 SSD and LSI 9211-8i (mpt2sas)
...<ffffffff814edcad>] wait_for_completion+0x1d/0x20 Oct 3 12:49:12 svfis-sg2 kernel: [<ffffffff812574a2>] blkdev_issue_discard+0x152/0x1e0 Oct 3 12:49:12 svfis-sg2 kernel: [<ffffffff81257e8f>] blkdev_ioctl+0x65f/0x6e0 Oct 3 12:49:12 svfis-sg2 kernel: [<ffffffff811aefcc>] block_ioctl+0x3c/0x40 Oct 3 12:49:12 svfis-sg2 kernel: [<ffffffff81189682>] vfs_ioctl+0x22/0xa0 Oct 3 12:49:12 svfis-sg2 kernel: [<ffffffff81189824>] do_vfs_ioctl+0x84/0x580 Oct 3 12:49:12 svfis-sg2 kernel: [<ffffffff81189da1>] sys_ioctl+0x81/0xa0 Oct 3 12:49:12 svfis-sg2 kernel: [<ff...
2020 Apr 30
0
[PATCH v3] virtio-blk: handle block_device_operations callbacks after hot unplug
...00 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > Call Trace: > [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] > [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 > [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 > [<ffffffff8d488771>] block_ioctl+0x41/0x50 > [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 > [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 > > A related problem is that virtblk_remove() leaks the vd_index_ida index > when something still holds a reference to vblk->disk during hot unplug. > This c...
2020 May 14
0
[PATCH AUTOSEL 5.6 32/62] virtio-blk: handle block_device_operations callbacks after hot unplug
...000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 [<ffffffff8d488771>] block_ioctl+0x41/0x50 [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 A related problem is that virtblk_remove() leaks the vd_index_ida index when something still holds a reference to vblk->disk during hot unplug. This causes virtio-blk device names...
2020 May 14
0
[PATCH AUTOSEL 4.19 22/31] virtio-blk: handle block_device_operations callbacks after hot unplug
...000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 [<ffffffff8d488771>] block_ioctl+0x41/0x50 [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 A related problem is that virtblk_remove() leaks the vd_index_ida index when something still holds a reference to vblk->disk during hot unplug. This causes virtio-blk device names...
2020 May 14
0
[PATCH AUTOSEL 4.14 31/39] virtio-blk: handle block_device_operations callbacks after hot unplug
...000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 [<ffffffff8d488771>] block_ioctl+0x41/0x50 [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 A related problem is that virtblk_remove() leaks the vd_index_ida index when something still holds a reference to vblk->disk during hot unplug. This causes virtio-blk device names...
2020 May 14
0
[PATCH AUTOSEL 5.4 29/49] virtio-blk: handle block_device_operations callbacks after hot unplug
...000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: [<ffffffffc016ac37>] virtblk_getgeo+0x47/0x110 [virtio_blk] [<ffffffff8d3f200d>] ? handle_mm_fault+0x39d/0x9b0 [<ffffffff8d561265>] blkdev_ioctl+0x1f5/0xa20 [<ffffffff8d488771>] block_ioctl+0x41/0x50 [<ffffffff8d45d9e0>] do_vfs_ioctl+0x3a0/0x5a0 [<ffffffff8d45dc81>] SyS_ioctl+0xa1/0xc0 A related problem is that virtblk_remove() leaks the vd_index_ida index when something still holds a reference to vblk->disk during hot unplug. This causes virtio-blk device names...