mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org
Cc: jjherne@linux.ibm.com, borntraeger@de.ibm.com,
	pasic@linux.ibm.com, alex@shazbot.org, kwankhede@nvidia.com,
	fiuczy@linux.ibm.com, pbonzini@redhat.com, frankja@linux.ibm.com,
	imbrenda@linux.ibm.com, agordeev@linux.ibm.com,
	hca@linux.ibm.com, gor@linux.ibm.com, stable@vger.kernel.org
Subject: Re: [PATCH v2 3/8] s390/vfio-ap: Fix use of wrong lock in mdev probe function
Date: Tue, 11 Aug 2026 14:42:54 -0400	[thread overview]
Message-ID: <00b0ea7d-bdeb-42d3-aad1-a8a827f2deb1@linux.ibm.com> (raw)
In-Reply-To: <4ca672ce-da47-497c-aed1-9500b7e89798@linux.ibm.com>



On 8/11/26 11:58 AM, Matthew Rosato wrote:
> On 8/10/26 3:22 PM, Anthony Krowiak wrote:
>> The vfio_ap_mdev_probe function uses the matrix_dev->mdevs_lock
>> mutex to guard the add of a newly created ap_matrix_mdev object to the
>> matrix_dev->mdev_list. This mutex does not protect against traversal
>> of the list; its purpose is to guard against concurrent access to fields
>> contained in an ap_matrix_mdev object. This could lead to kernel memory
>> corruption or use-after-free if another mdev is created concurrently.
>>
>> The adding of an ap_matrix_mdev object to matrix_dev->mdev_list
>> is now guarded by the matrix_dev->guests_lock which is the correct
>> way to protect against concurrent mdev_list access.
>>
>> See the vfio-ap-locking.rst in the linux kernel tree.
>>
>> Fixes: 2c1ee8983aa3 ("s390/vfio-ap: prepare for dynamic update of guest's APCB on queue probe/remove")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Anthony Krowiak <akrowiak@linux.ibm.com>
>> ---
>>   drivers/s390/crypto/vfio_ap_ops.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/s390/crypto/vfio_ap_ops.c b/drivers/s390/crypto/vfio_ap_ops.c
>> index e382e5a1cb99..a472de00bc14 100644
>> --- a/drivers/s390/crypto/vfio_ap_ops.c
>> +++ b/drivers/s390/crypto/vfio_ap_ops.c
>> @@ -803,9 +803,9 @@ static int vfio_ap_mdev_probe(struct mdev_device *mdev)
>>   	matrix_mdev->req_trigger = NULL;
>>   	matrix_mdev->cfg_chg_trigger = NULL;
>>   	dev_set_drvdata(&mdev->dev, matrix_mdev);
>> -	mutex_lock(&matrix_dev->mdevs_lock);
>> +	mutex_lock(&matrix_dev->guests_lock);
> Sashiko reports that this patch introduces a regression, which seems valid.
>
> AFAICT you resolve this regression with patch 7 of this series.
>
> For the sake of bisect, can you look at whether squashing these 2
> patches together would work so that we don't have an interim regression?

The reason for the two different patches is because the shah on the 
Fixes: tag
differ.

>
>


  reply	other threads:[~2026-08-11 18:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 19:22 [PATCH v2 0/8] s390/vfio-ap: Fix bugs in vfio_ap device driver callback functions Anthony Krowiak
2026-08-10 19:22 ` [PATCH v2 1/8] s390/vfio-ap: Fix stale do_remove flag across iterations in vfio_ap_mdev_cfg_remove Anthony Krowiak
2026-08-11 14:57   ` Matthew Rosato
2026-08-10 19:22 ` [PATCH v2 2/8] s390/vfio-ap: Fix dereference matrix_mdev->kvm without checking for NULL Anthony Krowiak
2026-08-11 15:53   ` Matthew Rosato
2026-08-10 19:22 ` [PATCH v2 3/8] s390/vfio-ap: Fix use of wrong lock in mdev probe function Anthony Krowiak
2026-08-11 15:58   ` Matthew Rosato
2026-08-11 18:42     ` Anthony Krowiak [this message]
2026-08-11 18:44       ` Matthew Rosato
2026-08-11 18:53         ` Anthony Krowiak
2026-08-10 19:22 ` [PATCH v2 4/8] s390/vfio-ap: Fix required lock not held during update of ap_matrix_mdev object Anthony Krowiak
2026-08-11 16:38   ` Matthew Rosato
2026-08-10 19:22 ` [PATCH v2 5/8] s390/vfio-ap: Fix control domain removal in vfio_ap_mdev_cfg_remove Anthony Krowiak
2026-08-11 17:14   ` Matthew Rosato
2026-08-10 19:22 ` [PATCH v2 6/8] s390/vfio-ap: fix potential use of uninitialized apm_filtered bitmap Anthony Krowiak
2026-08-11 18:02   ` Matthew Rosato
2026-08-11 19:24     ` Anthony Krowiak
2026-08-10 19:22 ` [PATCH v2 7/8] s390/vfio-ap: Fix required lock not held during display of sysfs status attribute Anthony Krowiak
2026-08-11 18:03   ` Matthew Rosato
2026-08-11 18:20     ` Matthew Rosato
2026-08-11 18:51       ` Anthony Krowiak
2026-08-11 18:55         ` Matthew Rosato
2026-08-11 20:19           ` Anthony Krowiak
2026-08-11 18:43     ` Anthony Krowiak
2026-08-10 19:22 ` [PATCH v2 8/8] s390/vfio-ap: Fix hot-unplug skipped when last AP adapter or domain removed Anthony Krowiak
2026-08-11 20:43   ` Matthew Rosato

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=00b0ea7d-bdeb-42d3-aad1-a8a827f2deb1@linux.ibm.com \
    --to=akrowiak@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=alex@shazbot.org \
    --cc=borntraeger@de.ibm.com \
    --cc=fiuczy@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=jjherne@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=pbonzini@redhat.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

all inboxes | Powered by JetHome®