* [PATCH 0/1] virtio/s390: one fix
@ 2015-12-03 16:23 Cornelia Huck
2015-12-03 16:24 ` [PATCH 1/1] virtio/s390: handle error values in irb Cornelia Huck
2015-12-14 15:02 ` [PATCH 0/1] virtio/s390: one fix Cornelia Huck
0 siblings, 2 replies; 4+ messages in thread
From: Cornelia Huck @ 2015-12-03 16:23 UTC (permalink / raw)
To: mst; +Cc: borntraeger, virtualization, kvm, linux-s390
Michael,
here's one fix for the virtio-ccw driver.
Patch is against master, as your git branches on mst/vhost.git seem
to be quite old. Is there some branch I can base my own branch on,
or do you prefer to take patches directly anyway?
Cornelia Huck (1):
virtio/s390: handle error values in irb
drivers/s390/virtio/virtio_ccw.c | 62 ++++++++++++++++++++++++----------------
1 file changed, 37 insertions(+), 25 deletions(-)
--
2.3.9
^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH 1/1] virtio/s390: handle error values in irb
2015-12-03 16:23 [PATCH 0/1] virtio/s390: one fix Cornelia Huck
@ 2015-12-03 16:24 ` Cornelia Huck
2015-12-14 15:02 ` [PATCH 0/1] virtio/s390: one fix Cornelia Huck
1 sibling, 0 replies; 4+ messages in thread
From: Cornelia Huck @ 2015-12-03 16:24 UTC (permalink / raw)
To: mst; +Cc: borntraeger, linux-s390, virtualization, kvm, Cornelia Huck
The common I/O layer may pass an error value as the irb in the device's
interrupt handler (for classic channel I/O). This won't happen in
current virtio-ccw implementations, but it's better to be safe than
sorry.
Let's just return the error conveyed by the irb and clear any possible
pending I/O indications.
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Reviewed-by: Guenther Hutzl <hutzl@linux.vnet.ibm.com>
Reviewed-by: Pierre Morel <pmorel@linux.vnet.ibm.com>
---
drivers/s390/virtio/virtio_ccw.c | 62 ++++++++++++++++++++++++----------------
1 file changed, 37 insertions(+), 25 deletions(-)
diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c
index b2a1a81..1b83159 100644
--- a/drivers/s390/virtio/virtio_ccw.c
+++ b/drivers/s390/virtio/virtio_ccw.c
@@ -984,6 +984,36 @@ static struct virtqueue *virtio_ccw_vq_by_ind(struct virtio_ccw_device *vcdev,
return vq;
}
+static void virtio_ccw_check_activity(struct virtio_ccw_device *vcdev,
+ __u32 activity)
+{
+ if (vcdev->curr_io & activity) {
+ switch (activity) {
+ case VIRTIO_CCW_DOING_READ_FEAT:
+ case VIRTIO_CCW_DOING_WRITE_FEAT:
+ case VIRTIO_CCW_DOING_READ_CONFIG:
+ case VIRTIO_CCW_DOING_WRITE_CONFIG:
+ case VIRTIO_CCW_DOING_WRITE_STATUS:
+ case VIRTIO_CCW_DOING_SET_VQ:
+ case VIRTIO_CCW_DOING_SET_IND:
+ case VIRTIO_CCW_DOING_SET_CONF_IND:
+ case VIRTIO_CCW_DOING_RESET:
+ case VIRTIO_CCW_DOING_READ_VQ_CONF:
+ case VIRTIO_CCW_DOING_SET_IND_ADAPTER:
+ case VIRTIO_CCW_DOING_SET_VIRTIO_REV:
+ vcdev->curr_io &= ~activity;
+ wake_up(&vcdev->wait_q);
+ break;
+ default:
+ /* don't know what to do... */
+ dev_warn(&vcdev->cdev->dev,
+ "Suspicious activity '%08x'\n", activity);
+ WARN_ON(1);
+ break;
+ }
+ }
+}
+
static void virtio_ccw_int_handler(struct ccw_device *cdev,
unsigned long intparm,
struct irb *irb)
@@ -995,6 +1025,12 @@ static void virtio_ccw_int_handler(struct ccw_device *cdev,
if (!vcdev)
return;
+ if (IS_ERR(irb)) {
+ vcdev->err = PTR_ERR(irb);
+ virtio_ccw_check_activity(vcdev, activity);
+ /* Don't poke around indicators, something's wrong. */
+ return;
+ }
/* Check if it's a notification from the host. */
if ((intparm == 0) &&
(scsw_stctl(&irb->scsw) ==
@@ -1010,31 +1046,7 @@ static void virtio_ccw_int_handler(struct ccw_device *cdev,
/* Map everything else to -EIO. */
vcdev->err = -EIO;
}
- if (vcdev->curr_io & activity) {
- switch (activity) {
- case VIRTIO_CCW_DOING_READ_FEAT:
- case VIRTIO_CCW_DOING_WRITE_FEAT:
- case VIRTIO_CCW_DOING_READ_CONFIG:
- case VIRTIO_CCW_DOING_WRITE_CONFIG:
- case VIRTIO_CCW_DOING_WRITE_STATUS:
- case VIRTIO_CCW_DOING_SET_VQ:
- case VIRTIO_CCW_DOING_SET_IND:
- case VIRTIO_CCW_DOING_SET_CONF_IND:
- case VIRTIO_CCW_DOING_RESET:
- case VIRTIO_CCW_DOING_READ_VQ_CONF:
- case VIRTIO_CCW_DOING_SET_IND_ADAPTER:
- case VIRTIO_CCW_DOING_SET_VIRTIO_REV:
- vcdev->curr_io &= ~activity;
- wake_up(&vcdev->wait_q);
- break;
- default:
- /* don't know what to do... */
- dev_warn(&cdev->dev, "Suspicious activity '%08x'\n",
- activity);
- WARN_ON(1);
- break;
- }
- }
+ virtio_ccw_check_activity(vcdev, activity);
for_each_set_bit(i, &vcdev->indicators,
sizeof(vcdev->indicators) * BITS_PER_BYTE) {
/* The bit clear must happen before the vring kick. */
--
2.3.9
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH 0/1] virtio/s390: one fix
2015-12-03 16:23 [PATCH 0/1] virtio/s390: one fix Cornelia Huck
2015-12-03 16:24 ` [PATCH 1/1] virtio/s390: handle error values in irb Cornelia Huck
@ 2015-12-14 15:02 ` Cornelia Huck
2015-12-14 15:25 ` Michael S. Tsirkin
1 sibling, 1 reply; 4+ messages in thread
From: Cornelia Huck @ 2015-12-14 15:02 UTC (permalink / raw)
To: mst; +Cc: borntraeger, virtualization, kvm, linux-s390
On Thu, 3 Dec 2015 17:23:59 +0100
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> Michael,
>
> here's one fix for the virtio-ccw driver.
>
> Patch is against master, as your git branches on mst/vhost.git seem
> to be quite old. Is there some branch I can base my own branch on,
> or do you prefer to take patches directly anyway?
>
> Cornelia Huck (1):
> virtio/s390: handle error values in irb
>
> drivers/s390/virtio/virtio_ccw.c | 62 ++++++++++++++++++++++++----------------
> 1 file changed, 37 insertions(+), 25 deletions(-)
>
Ping?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 0/1] virtio/s390: one fix
2015-12-14 15:02 ` [PATCH 0/1] virtio/s390: one fix Cornelia Huck
@ 2015-12-14 15:25 ` Michael S. Tsirkin
0 siblings, 0 replies; 4+ messages in thread
From: Michael S. Tsirkin @ 2015-12-14 15:25 UTC (permalink / raw)
To: Cornelia Huck; +Cc: borntraeger, linux-s390, virtualization, kvm
On Mon, Dec 14, 2015 at 04:02:33PM +0100, Cornelia Huck wrote:
> On Thu, 3 Dec 2015 17:23:59 +0100
> Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
>
> > Michael,
> >
> > here's one fix for the virtio-ccw driver.
> >
> > Patch is against master, as your git branches on mst/vhost.git seem
> > to be quite old. Is there some branch I can base my own branch on,
> > or do you prefer to take patches directly anyway?
> >
> > Cornelia Huck (1):
> > virtio/s390: handle error values in irb
> >
> > drivers/s390/virtio/virtio_ccw.c | 62 ++++++++++++++++++++++++----------------
> > 1 file changed, 37 insertions(+), 25 deletions(-)
> >
>
> Ping?
Thanks, I'll merge this, hope it can still make 4.4.
--
MST
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-12-14 15:25 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-12-03 16:23 [PATCH 0/1] virtio/s390: one fix Cornelia Huck
2015-12-03 16:24 ` [PATCH 1/1] virtio/s390: handle error values in irb Cornelia Huck
2015-12-14 15:02 ` [PATCH 0/1] virtio/s390: one fix Cornelia Huck
2015-12-14 15:25 ` Michael S. Tsirkin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox