All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: stable@vger.kernel.org, farman@linux.ibm.com
Subject: Re: [PATCH 4.14-stable backport] vfio: ccw: only free cp on final interrupt
Date: Mon, 1 Apr 2019 15:52:44 +0200	[thread overview]
Message-ID: <20190401135244.GA23581@kroah.com> (raw)
In-Reply-To: <20190401131425.9536-1-cohuck@redhat.com>

On Mon, Apr 01, 2019 at 03:14:25PM +0200, Cornelia Huck wrote:
> When we get an interrupt for a channel program, it is not
> necessarily the final interrupt; for example, the issuing
> guest may request an intermediate interrupt by specifying
> the program-controlled-interrupt flag on a ccw.
> 
> We must not switch the state to idle if the interrupt is not
> yet final; even more importantly, we must not free the translated
> channel program if the interrupt is not yet final, or the host
> can crash during cp rewind.
> 
> Fixes: e5f84dbaea59 ("vfio: ccw: return I/O results asynchronously")
> Cc: stable@vger.kernel.org # v4.12+
> Reviewed-by: Eric Farman <farman@linux.ibm.com>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> (cherry picked from commit 50b7f1b7236bab08ebbbecf90521e84b068d7a17)
> ---
>  drivers/s390/cio/vfio_ccw_drv.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)

Now queued up, thanks.

greg k-h

      reply	other threads:[~2019-04-01 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 13:14 [PATCH 4.14-stable backport] vfio: ccw: only free cp on final interrupt Cornelia Huck
2019-04-01 13:52 ` Greg KH [this message]

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=20190401135244.GA23581@kroah.com \
    --to=greg@kroah.com \
    --cc=cohuck@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=stable@vger.kernel.org \
    /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.