From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Tony Krowiak <akrowiak@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Cc: jjherne@linux.ibm.com, pasic@linux.ibm.com,
frankja@linux.ibm.com, imbrenda@linux.ibm.com, david@redhat.com,
Matthew Rosato <mjrosato@linux.ibm.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/3] s390/vfio-ap: unpin pages on gisc registration failure
Date: Thu, 26 Oct 2023 14:18:47 +0200 [thread overview]
Message-ID: <c6951c45-b091-11a6-5684-ba2ef0c94df3@linux.ibm.com> (raw)
In-Reply-To: <20231018133829.147226-2-akrowiak@linux.ibm.com>
Am 18.10.23 um 15:38 schrieb Tony Krowiak:
> From: Anthony Krowiak <akrowiak@linux.ibm.com>
>
> In the vfio_ap_irq_enable function, after the page containing the
> notification indicator byte (NIB) is pinned, the function attempts
> to register the guest ISC. If registration fails, the function sets the
> status response code and returns without unpinning the page containing
> the NIB. In order to avoid a memory leak, the NIB should be unpinned before
> returning from the vfio_ap_irq_enable function.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Where is Janoschs signed off coming from here?
> Signed-off-by: Anthony Krowiak <akrowiak@linux.ibm.com>
> Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
> Fixes: 783f0a3ccd79 ("s390/vfio-ap: add s390dbf logging to the vfio_ap_irq_enable function")
> Cc: <stable@vger.kernel.org>
> ---
> drivers/s390/crypto/vfio_ap_ops.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/s390/crypto/vfio_ap_ops.c b/drivers/s390/crypto/vfio_ap_ops.c
> index 4db538a55192..9cb28978c186 100644
> --- a/drivers/s390/crypto/vfio_ap_ops.c
> +++ b/drivers/s390/crypto/vfio_ap_ops.c
> @@ -457,6 +457,7 @@ static struct ap_queue_status vfio_ap_irq_enable(struct vfio_ap_queue *q,
> VFIO_AP_DBF_WARN("%s: gisc registration failed: nisc=%d, isc=%d, apqn=%#04x\n",
> __func__, nisc, isc, q->apqn);
>
> + vfio_unpin_pages(&q->matrix_mdev->vdev, nib, 1);
> status.response_code = AP_RESPONSE_INVALID_GISA;
> return status;
> }
next prev parent reply other threads:[~2023-10-26 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 13:38 [PATCH v2 0/3] a couple of corrections to the IRQ enablement function Tony Krowiak
2023-10-18 13:38 ` [PATCH v2 1/3] s390/vfio-ap: unpin pages on gisc registration failure Tony Krowiak
2023-10-26 12:18 ` Christian Borntraeger [this message]
2023-10-26 13:16 ` Tony Krowiak
2023-10-26 13:25 ` Christian Borntraeger
2023-10-26 14:20 ` Tony Krowiak
2023-10-18 13:38 ` [PATCH v2 2/3] s390/vfio-ap: set status response code to 06 " Tony Krowiak
2023-10-27 10:56 ` Halil Pasic
[not found] ` <8eb41445-1eff-4da7-830f-156f420afd5d@linux.ibm.com>
[not found] ` <20231027160347.05c6cd60.pasic@linux.ibm.com>
2023-10-27 17:06 ` Tony Krowiak
2023-10-18 13:38 ` [PATCH v2 3/3] s390/vfio-ap: improve reaction to response code 07 from PQAP(AQIC) command Tony Krowiak
2023-10-26 14:15 ` Matthew Rosato
2023-10-26 18:18 ` Tony Krowiak
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=c6951c45-b091-11a6-5684-ba2ef0c94df3@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox