From: Jason Gunthorpe <jgg@nvidia.com>
To: liulongfang <liulongfang@huawei.com>
Cc: John Garry <john.garry@huawei.com>,
alex.williamson@redhat.com, shameerali.kolothum.thodi@huawei.com,
cohuck@redhat.com, linux-kernel@vger.kernel.org,
linuxarm@openeuler.org
Subject: Re: [Linuxarm] [PATCH 1/2] hisi_acc_vfio_pci: Add debugfs to migration driver
Date: Tue, 18 Oct 2022 09:01:38 -0300 [thread overview]
Message-ID: <Y06Voma/Prezqmag@nvidia.com> (raw)
In-Reply-To: <9826a418-4a14-aa4a-9eb8-6faf3e43c8e3@huawei.com>
On Tue, Oct 18, 2022 at 03:06:43PM +0800, liulongfang wrote:
> On 2022/10/17 20:11, Jason Gunthorpe Wrote:
> > On Mon, Oct 17, 2022 at 05:20:34PM +0800, liulongfang wrote:
> >> On 2022/10/14 17:20, John Garry wrote:
> >>> On 14/10/2022 03:57, Longfang Liu wrote:
> >>>> +static void hisi_acc_vf_debugfs_init(struct hisi_acc_vf_core_device *hisi_acc_vdev)
> >>>> +{
> >>>> + struct pci_dev *vf_pdev = hisi_acc_vdev->vf_dev;
> >>>> + struct device *dev = &vf_pdev->dev;
> >>>> + int ret;
> >>>> +
> >>>> + if (!atomic_read(&hisi_acc_root_ref))
> >>>> + hisi_acc_debugfs_root = debugfs_create_dir("hisi_vfio_acc", NULL);
> >>>> + atomic_inc(&hisi_acc_root_ref);
> >>>> +
> >>>
> >>> This looks totally racy, such that I wonder why even bother using an atomic for hisi_acc_root_ref.
> >>
> >>
> >> When enabling VF, it is possible for multiple VMs to enable VF at the same time. The atomic variable
> >> is used to ensure that only one "hisi_vfio_acc" is created. When other VFs are enabled,
> >> it will not be created again, but will be used directly.
> >
> > It is still completely racy. Use a lock
> >
>
> Do you have any suggested solutions?
If you want to keep it like this, use a lock around the creation.
Jason
next prev parent reply other threads:[~2022-10-18 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 2:57 [PATCH 0/2] Add debugfs to hisilicon migration driver Longfang Liu
2022-10-14 2:57 ` [PATCH 1/2] hisi_acc_vfio_pci: Add debugfs to " Longfang Liu
2022-10-14 9:20 ` [Linuxarm] " John Garry
2022-10-17 9:20 ` liulongfang
2022-10-17 12:11 ` Jason Gunthorpe
2022-10-18 7:06 ` liulongfang
2022-10-18 12:01 ` Jason Gunthorpe [this message]
2022-10-19 7:17 ` liulongfang
2022-10-17 13:57 ` Shameerali Kolothum Thodi
2022-10-18 6:55 ` liulongfang
2022-10-18 7:05 ` liulongfang
2022-10-14 2:57 ` [PATCH 2/2] Documentation: Add debugfs for hisi_acc_vfio_pci Longfang Liu
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=Y06Voma/Prezqmag@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=liulongfang@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.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