mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Brett Creeley <brett.creeley@amd.com>
Cc: <jgg@ziepe.ca>, <yishaih@nvidia.com>,
	<shameerali.kolothum.thodi@huawei.com>, <kevin.tian@intel.com>,
	<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<shannon.nelson@amd.com>
Subject: Re: [PATCH v4 vfio 0/2] vfio/pds: Fixes for locking bugs
Date: Mon, 27 Nov 2023 11:08:50 -0700	[thread overview]
Message-ID: <20231127110850.3e4f527a.alex.williamson@redhat.com> (raw)
In-Reply-To: <20231122192532.25791-1-brett.creeley@amd.com>

On Wed, 22 Nov 2023 11:25:30 -0800
Brett Creeley <brett.creeley@amd.com> wrote:

> This series contains fixes for locking bugs in the recently introduced
> pds-vfio-pci driver. There was an initial bug reported by Dan Carpenter
> at:
> 
> https://lore.kernel.org/kvm/1f9bc27b-3de9-4891-9687-ba2820c1b390@moroto.mountain/
> 
> However, more locking bugs were found when looking into the previously
> mentioned issue. So, all fixes are included in this series.
> 
> v4:
> - Drop patch 1/3 since it added a spinlock_init that was later replaced
>   by a mutex_init anyway
> 
> v3:
> https://lore.kernel.org/kvm/20231027223651.36047-1-brett.creeley@amd.com/
> - Change reset lock from spinlock to mutex
> 
> v2:
> https://lore.kernel.org/kvm/20231011230115.35719-1-brett.creeley@amd.com/
> - Trim the OOPs in the patch commit messages
> - Rework patch 3/3 to only unlock the spinlock once
> - Destroy the state_mutex in the driver specific vfio_device_ops.release
>   callback
> 
> v1:
> https://lore.kernel.org/kvm/20230914191540.54946-1-brett.creeley@amd.com/
> 
> Brett Creeley (2):
>   vfio/pds: Fix mutex lock->magic != lock warning
>   vfio/pds: Fix possible sleep while in atomic context
> 
>  drivers/vfio/pci/pds/pci_drv.c  |  4 ++--
>  drivers/vfio/pci/pds/vfio_dev.c | 30 +++++++++++++++++++++---------
>  drivers/vfio/pci/pds/vfio_dev.h |  2 +-
>  3 files changed, 24 insertions(+), 12 deletions(-)
> 

Applied to vfio for-linus branch for v6.7.  Thanks,

Alex


      parent reply	other threads:[~2023-11-27 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 19:25 Brett Creeley
2023-11-22 19:25 ` [PATCH v4 vfio 1/2] vfio/pds: Fix mutex lock->magic != lock warning Brett Creeley
2023-11-22 19:25 ` [PATCH v4 vfio 2/2] vfio/pds: Fix possible sleep while in atomic context Brett Creeley
2023-11-27 18:08 ` Alex Williamson [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=20231127110850.3e4f527a.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=brett.creeley@amd.com \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=shannon.nelson@amd.com \
    --cc=yishaih@nvidia.com \
    /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®