From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Cc: jjherne@linux.ibm.com, pasic@linux.ibm.com, hca@linux.ibm.com,
gor@linux.ibm.com, borntraeger@linux.ibm.com,
alex.williamson@redhat.com, clg@redhat.com,
mjrosato@linux.ibm.com, stable@vger.kernel.org
Subject: Re: [PATCH] s390/vfio-ap: lock mdev object when handling mdev remove request
Date: Tue, 11 Mar 2025 06:34:20 -0400 [thread overview]
Message-ID: <ff033f2a-b82c-4c7b-a45d-71c674892b2d@linux.ibm.com> (raw)
In-Reply-To: <20250221153238.3242737-1-akrowiak@linux.ibm.com>
PING!
On 2/21/25 10:32 AM, Anthony Krowiak wrote:
> The vfio_ap_mdev_request function in drivers/s390/crypto/vfio_ap_ops.c
> accesses fields of an ap_matrix_mdev object without ensuring that the
> object is accessed by only one thread at a time. This patch adds the lock
> necessary to secure access to the ap_matrix_mdev object.
>
> Fixes: 2e3d8d71e285 ("s390/vfio-ap: wire in the vfio_device_ops request callback")
> Signed-off-by: Anthony Krowiak <akrowiak@linux.ibm.com>
> Cc: <stable@vger.kernel.org>
> ---
> drivers/s390/crypto/vfio_ap_ops.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/s390/crypto/vfio_ap_ops.c b/drivers/s390/crypto/vfio_ap_ops.c
> index a52c2690933f..a2784d3357d9 100644
> --- a/drivers/s390/crypto/vfio_ap_ops.c
> +++ b/drivers/s390/crypto/vfio_ap_ops.c
> @@ -2045,6 +2045,7 @@ static void vfio_ap_mdev_request(struct vfio_device *vdev, unsigned int count)
> struct ap_matrix_mdev *matrix_mdev;
>
> matrix_mdev = container_of(vdev, struct ap_matrix_mdev, vdev);
> + mutex_lock(&matrix_dev->mdevs_lock);
>
> if (matrix_mdev->req_trigger) {
> if (!(count % 10))
> @@ -2057,6 +2058,8 @@ static void vfio_ap_mdev_request(struct vfio_device *vdev, unsigned int count)
> dev_notice(dev,
> "No device request registered, blocked until released by user\n");
> }
> +
> + mutex_unlock(&matrix_dev->mdevs_lock);
> }
>
> static int vfio_ap_mdev_get_device_info(unsigned long arg)
next prev parent reply other threads:[~2025-03-11 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 15:32 [PATCH] s390/vfio-ap: lock mdev object when handling mdev remove request Anthony Krowiak
2025-03-11 10:34 ` Anthony Krowiak [this message]
2025-03-12 15:19 ` Matthew Rosato
2025-03-13 11:18 ` Anthony 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=ff033f2a-b82c-4c7b-a45d-71c674892b2d@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hca@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