| Message ID | 20220728204914.2420989-4-farman@linux.ibm.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | vfio-ccw fixes for 5.20 | expand |
On Thu, Jul 28, 2022 at 10:49:14PM +0200, Eric Farman wrote: > If a subchannel is busy when a close is performed, the subchannel > needs to be quiesced and left nice and tidy, so nothing unexpected > (like a solicited interrupt) shows up while in the closed state. > Unfortunately, the return code from this call isn't checked, > so any busy subchannel is treated as a failing one. > > Fix that, so that the close on a busy subchannel happens normally. > > Signed-off-by: Eric Farman <farman@linux.ibm.com> > Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com> > --- > drivers/s390/cio/vfio_ccw_fsm.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> Jason
diff --git a/drivers/s390/cio/vfio_ccw_fsm.c b/drivers/s390/cio/vfio_ccw_fsm.c index 4b8b623df24f..a59c758869f8 100644 --- a/drivers/s390/cio/vfio_ccw_fsm.c +++ b/drivers/s390/cio/vfio_ccw_fsm.c @@ -407,7 +407,7 @@ static void fsm_close(struct vfio_ccw_private *private, ret = cio_disable_subchannel(sch); if (ret == -EBUSY) - vfio_ccw_sch_quiesce(sch); + ret = vfio_ccw_sch_quiesce(sch); if (ret) goto err_unlock;