All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Gleb Natapov <gleb@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Carsten Otte <cotte@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	KVM <kvm@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [PATCH] KVM: s390: virtio_ccw: reset errors for new I/O.
Date: Thu, 4 Apr 2013 12:20:03 +0200	[thread overview]
Message-ID: <20130404122003.17bd05fa@gondolin> (raw)
In-Reply-To: <FFC59559-C498-4EA4-971A-A61436932654@suse.de>

On Thu, 4 Apr 2013 11:28:35 +0200
Alexander Graf <agraf@suse.de> wrote:

> 
> On 04.04.2013, at 10:25, Cornelia Huck wrote:
> 
> > ccw_io_helper neglected to reset vcdev->err after a new channel
> > program had been successfully started, resulting in stale errors
> > delivered after one I/O failed. Reset the error after a new
> > channel program has been successfully started with no old I/O
> > pending.
> > 
> > Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> 
> Shouldn't this be CC: stable?

I don't think so, current code will not continue after errors anyway.

> 
> 
> Alex
> 
> > ---
> > drivers/s390/kvm/virtio_ccw.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/s390/kvm/virtio_ccw.c b/drivers/s390/kvm/virtio_ccw.c
> > index 42d507c..5948f2a 100644
> > --- a/drivers/s390/kvm/virtio_ccw.c
> > +++ b/drivers/s390/kvm/virtio_ccw.c
> > @@ -133,8 +133,11 @@ static int ccw_io_helper(struct virtio_ccw_device *vcdev,
> > 	do {
> > 		spin_lock_irqsave(get_ccwdev_lock(vcdev->cdev), flags);
> > 		ret = ccw_device_start(vcdev->cdev, ccw, intparm, 0, 0);
> > -		if (!ret)
> > +		if (!ret) {
> > +			if (!vcdev->curr_io)
> > +				vcdev->err = 0;
> > 			vcdev->curr_io |= flag;
> > +		}
> > 		spin_unlock_irqrestore(get_ccwdev_lock(vcdev->cdev), flags);
> > 		cpu_relax();
> > 	} while (ret == -EBUSY);
> > -- 
> > 1.7.12.4
> > 
> 

  reply	other threads:[~2013-04-04 10:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  8:25 [PATCH] KVM: s390: virtio-ccw bugfix Cornelia Huck
2013-04-04  8:25 ` [PATCH] KVM: s390: virtio_ccw: reset errors for new I/O Cornelia Huck
2013-04-04  9:28   ` Alexander Graf
2013-04-04 10:20     ` Cornelia Huck [this message]
2013-04-04 11:34       ` Alexander Graf
2013-04-04  8:27 ` [PATCH] KVM: s390: virtio-ccw bugfix Gleb Natapov
2013-04-04  8:35   ` Cornelia Huck
2013-04-04  9:00     ` Gleb Natapov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130404122003.17bd05fa@gondolin \
    --to=cornelia.huck@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=gleb@redhat.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=schwidefsky@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.