From: Bjorn Helgaas <helgaas@kernel.org>
To: CREGUT Pierre IMT/OLN <pierre.cregut@orange.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Donald Dutile <ddutile@redhat.com>,
Alexander Duyck <alexander.h.duyck@intel.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: Re: [PATCH] PCI/IOV: update num_VFs earlier
Date: Tue, 8 Oct 2019 16:38:35 -0500 [thread overview]
Message-ID: <20191008213835.GA230403@google.com> (raw)
In-Reply-To: <20191003221007.GA209602@google.com>
On Thu, Oct 03, 2019 at 05:10:07PM -0500, Bjorn Helgaas wrote:
> On Thu, Oct 03, 2019 at 11:04:45AM +0200, CREGUT Pierre IMT/OLN wrote:
> > ...
> > NIC drivers send netlink events when their state change, but it is
> > the core that changes the value of num_vfs. So I would think it is
> > the core responsibility to make sure the exposed value makes sense
> > and it would be better to ignore the details of the driver
> > implementation.
>
> Yes, I think you're right. And I like your previous suggestion of
> just locking the device in the reader. I'm not enough of a sysfs
> expert to know if there's a good reason to avoid a lock there. Does
> the following look reasonable to you?
I applied the patch below to pci/virtualization for v5.5, thanks for
your great patience!
> commit 0940fc95da45
> Author: Pierre Crégut <pierre.cregut@orange.com>
> Date: Wed Sep 11 09:27:36 2019 +0200
>
> PCI/IOV: Serialize sysfs sriov_numvfs reads vs writes
>
> When sriov_numvfs is being updated, drivers may notify about new devices
> before they are reflected in sriov->num_VFs, so concurrent sysfs reads
> previously returned stale values.
>
> Serialize the sysfs read vs the write so the read returns the correct
> num_VFs value.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=202991
> Link: https://lore.kernel.org/r/20190911072736.32091-1-pierre.cregut@orange.com
> Signed-off-by: Pierre Crégut <pierre.cregut@orange.com>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
>
> diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
> index b3f972e8cfed..e77562aabbae 100644
> --- a/drivers/pci/iov.c
> +++ b/drivers/pci/iov.c
> @@ -254,8 +254,14 @@ static ssize_t sriov_numvfs_show(struct device *dev,
> char *buf)
> {
> struct pci_dev *pdev = to_pci_dev(dev);
> + u16 num_vfs;
> +
> + /* Serialize vs sriov_numvfs_store() so readers see valid num_VFs */
> + device_lock(&pdev->dev);
> + num_vfs = pdev->sriov->num_VFs;
> + device_lock(&pdev->dev);
>
> - return sprintf(buf, "%u\n", pdev->sriov->num_VFs);
> + return sprintf(buf, "%u\n", num_vfs);
> }
>
> /*
next prev parent reply other threads:[~2019-10-08 21:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 8:00 [PATCH] PCI/IOV: update num_VFs earlier Pierre Crégut
2019-04-05 22:33 ` Bjorn Helgaas
2019-04-26 8:11 ` CREGUT Pierre IMT/OLN
2019-06-13 23:51 ` Bjorn Helgaas
2019-10-01 23:45 ` Bjorn Helgaas
2019-10-03 9:04 ` CREGUT Pierre IMT/OLN
2019-10-03 22:10 ` Bjorn Helgaas
2019-10-03 22:36 ` Jakub Kicinski
2019-10-03 22:37 ` Duyck, Alexander H
2019-10-08 21:38 ` Bjorn Helgaas [this message]
2019-10-08 22:06 ` Don Dutile
2019-10-09 12:31 ` Bjorn Helgaas
2019-10-09 14:20 ` Don Dutile
-- strict thread matches above, loose matches on Subject: below --
2019-03-25 8:18 Pierre Crégut
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=20191008213835.GA230403@google.com \
--to=helgaas@kernel.org \
--cc=alexander.h.duyck@intel.com \
--cc=ddutile@redhat.com \
--cc=jakub.kicinski@netronome.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pierre.cregut@orange.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;
as well as URLs for NNTP newsgroup(s).