search for: device_lost

...should be prevented by setting appropriate queue flags prior to invoking del_gendisk(). Blocking of request queueing leads to appropriate I/O errors when data are tried to be synched. Trying to synch data to a lost block device doesn't make too much sense. Calling blk_cleanup_queue() when the device_lost flag is set due to a disappeared device. It avoid hangs due to incomplete requests (e.g. in-flight requests). Such requests must be considered as lost. Signed-off-by: Heinz Graalfs <graalfs at linux.vnet.ibm.com> Acked-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- drivers/block/...

When a device is lost, the common I/O layer calls the notification handler with CIO_GONE: In that event, flag device_lost as true. In case the device had been flagged as lost when the remove/offline callbacks are called, call the new virtio_break_device() function prior to invoking device_unregister(). This avoids hangs of I/O triggered via the device unregistration callbacks. Signed-off-by: Heinz Graalfs <graalf...

...flag to the remove callback of the backend driver, can solve this task. v3->v4 changes: - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() callback processing). - patch 2: introduces 'device_lost' atomic in virtio_device and use in backend driver virtio_blk accordingly (original 3 patches merged). - patch 3: the notify() callback is now serialized with remove()/set_offline() callbacks. The notification is ignored if the vcdev pointer has been cleared already (by remove() or se...

...flag to the remove callback of the backend driver, can solve this task. v3->v4 changes: - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() callback processing). - patch 2: introduces 'device_lost' atomic in virtio_device and use in backend driver virtio_blk accordingly (original 3 patches merged). - patch 3: the notify() callback is now serialized with remove()/set_offline() callbacks. The notification is ignored if the vcdev pointer has been cleared already (by remove() or se...

...f the backend driver, can solve this task. > > v3->v4 changes: > - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver > (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() > callback processing). > - patch 2: introduces 'device_lost' atomic in virtio_device and use in > backend driver virtio_blk accordingly (original 3 patches merged). > - patch 3: the notify() callback is now serialized with remove()/set_offline() > callbacks. The notification is ignored if the vcdev pointer has been cleared > alread...

...f the backend driver, can solve this task. > > v3->v4 changes: > - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver > (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() > callback processing). > - patch 2: introduces 'device_lost' atomic in virtio_device and use in > backend driver virtio_blk accordingly (original 3 patches merged). > - patch 3: the notify() callback is now serialized with remove()/set_offline() > callbacks. The notification is ignored if the vcdev pointer has been cleared > alread...

When a CIO_GONE notification is received the device_lost flag is set in the virtio_device. This flag should be tested by a backend in order to be able to prevent triggering final I/O to a device that is not reachable any more. The notification is ignored in case remove or set_offline is already running. The virtio_device pointer might point to freed mem...

...sty, this patch exploits the new function virtio_break_device() as of your patch set dated January 15th on linux-kernel at vger.kernel.org. The patch avoids hang situations during device unregister, when a (block) device with active IO is hot-unplugged. Heinz Graalfs (1): virtio_ccw: introduce device_lost in virtio_ccw_device drivers/s390/kvm/virtio_ccw.c | 49 ++++++++++++++++++++++++++++++++----------- 1 file changed, 37 insertions(+), 12 deletions(-) -- 1.8.3.1

...sty, this patch exploits the new function virtio_break_device() as of your patch set dated January 15th on linux-kernel at vger.kernel.org. The patch avoids hang situations during device unregister, when a (block) device with active IO is hot-unplugged. Heinz Graalfs (1): virtio_ccw: introduce device_lost in virtio_ccw_device drivers/s390/kvm/virtio_ccw.c | 49 ++++++++++++++++++++++++++++++++----------- 1 file changed, 37 insertions(+), 12 deletions(-) -- 1.8.3.1

...gt; >>> v3->v4 changes: >>> - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver >>> (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() >>> callback processing). >>> - patch 2: introduces 'device_lost' atomic in virtio_device and use in >>> backend driver virtio_blk accordingly (original 3 patches merged). >>> - patch 3: the notify() callback is now serialized with remove()/set_offline() >>> callbacks. The notification is ignored if the vcdev pointer has...

...gt; >>> v3->v4 changes: >>> - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver >>> (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() >>> callback processing). >>> - patch 2: introduces 'device_lost' atomic in virtio_device and use in >>> backend driver virtio_blk accordingly (original 3 patches merged). >>> - patch 3: the notify() callback is now serialized with remove()/set_offline() >>> callbacks. The notification is ignored if the vcdev pointer has...

...lve this task. >> >> v3->v4 changes: >> - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver >> (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() >> callback processing). >> - patch 2: introduces 'device_lost' atomic in virtio_device and use in >> backend driver virtio_blk accordingly (original 3 patches merged). >> - patch 3: the notify() callback is now serialized with remove()/set_offline() >> callbacks. The notification is ignored if the vcdev pointer has been cleared...

...lve this task. >> >> v3->v4 changes: >> - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver >> (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() >> callback processing). >> - patch 2: introduces 'device_lost' atomic in virtio_device and use in >> backend driver virtio_blk accordingly (original 3 patches merged). >> - patch 3: the notify() callback is now serialized with remove()/set_offline() >> callbacks. The notification is ignored if the vcdev pointer has been cleared...

...>v4 changes: >>>> - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver >>>> (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() >>>> callback processing). >>>> - patch 2: introduces 'device_lost' atomic in virtio_device and use in >>>> backend driver virtio_blk accordingly (original 3 patches merged). >>>> - patch 3: the notify() callback is now serialized with remove()/set_offline() >>>> callbacks. The notification is ignored if the vcd...

...>v4 changes: >>>> - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver >>>> (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() >>>> callback processing). >>>> - patch 2: introduces 'device_lost' atomic in virtio_device and use in >>>> backend driver virtio_blk accordingly (original 3 patches merged). >>>> - patch 3: the notify() callback is now serialized with remove()/set_offline() >>>> callbacks. The notification is ignored if the vcd...

...lve this task. >> >> v3->v4 changes: >> - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver >> (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() >> callback processing). >> - patch 2: introduces 'device_lost' atomic in virtio_device and use in >> backend driver virtio_blk accordingly (original 3 patches merged). >> - patch 3: the notify() callback is now serialized with remove()/set_offline() >> callbacks. The notification is ignored if the vcdev pointer has been cleared...

...lve this task. >> >> v3->v4 changes: >> - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver >> (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() >> callback processing). >> - patch 2: introduces 'device_lost' atomic in virtio_device and use in >> backend driver virtio_blk accordingly (original 3 patches merged). >> - patch 3: the notify() callback is now serialized with remove()/set_offline() >> callbacks. The notification is ignored if the vcdev pointer has been cleared...

Heinz Graalfs <graalfs at linux.vnet.ibm.com> writes: > On 29/01/14 07:31, Rusty Russell wrote: >> Heinz Graalfs <graalfs at linux.vnet.ibm.com> writes: >>> On 23/01/14 05:51, Rusty Russell wrote: >>>> Heinz Graalfs <graalfs at linux.vnet.ibm.com> writes: >>>>> Hi, here is my v4 patch-set update to the v3 RFC submitted on Nov 27th.

...>v4 changes: >>>> - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver >>>> (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() >>>> callback processing). >>>> - patch 2: introduces 'device_lost' atomic in virtio_device and use in >>>> backend driver virtio_blk accordingly (original 3 patches merged). >>>> - patch 3: the notify() callback is now serialized with remove()/set_offline() >>>> callbacks. The notification is ignored if the vcd...

...>v4 changes: >>>> - patch 1: solves some vcdev pointer handling issues in the virtio_ccw driver >>>> (e.g. locked vcdev pointer reset/query; serialize remove()/set_offline() >>>> callback processing). >>>> - patch 2: introduces 'device_lost' atomic in virtio_device and use in >>>> backend driver virtio_blk accordingly (original 3 patches merged). >>>> - patch 3: the notify() callback is now serialized with remove()/set_offline() >>>> callbacks. The notification is ignored if the vcd...