From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yao Hongbo <yaohongbo@linux.alibaba.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
alikernel-developer@linux.alibaba.com
Subject: Re: [PATCH RESEND] uio/uio_pci_generic: Introduce refcnt on open/release
Date: Thu, 31 Mar 2022 16:30:00 -0400 [thread overview]
Message-ID: <20220331162952-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1648693432-129409-1-git-send-email-yaohongbo@linux.alibaba.com>
On Thu, Mar 31, 2022 at 10:23:52AM +0800, Yao Hongbo wrote:
> If two userspace programs both open the PCI UIO fd, when one
> of the program exits uncleanly, the other will cause IO hang
> due to bus-mastering disabled.
With two programs poking at the same device, how is this ever
supposed to work even while both are alive?
> It's a common usage for spdk/dpdk to use UIO. So, introduce refcnt
> to avoid such problems.
>
> Fixes: 865a11f("uio/uio_pci_generic: Disable bus-mastering on release")
> Reported-by: Xiu Yang <yangxiu.yx@alibaba-inc.com>
> Signed-off-by: Yao Hongbo <yaohongbo@linux.alibaba.com>
> ---
> drivers/uio/uio_pci_generic.c | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/uio/uio_pci_generic.c b/drivers/uio/uio_pci_generic.c
> index e03f9b5..8add2cf 100644
> --- a/drivers/uio/uio_pci_generic.c
> +++ b/drivers/uio/uio_pci_generic.c
> @@ -31,6 +31,7 @@
> struct uio_pci_generic_dev {
> struct uio_info info;
> struct pci_dev *pdev;
> + atomic_t refcnt;
> };
>
> static inline struct uio_pci_generic_dev *
> @@ -39,6 +40,14 @@ struct uio_pci_generic_dev {
> return container_of(info, struct uio_pci_generic_dev, info);
> }
>
> +static int open(struct uio_info *info, struct inode *inode)
> +{
> + struct uio_pci_generic_dev *gdev = to_uio_pci_generic_dev(info);
> +
> + atomic_inc(&gdev->refcnt);
> + return 0;
> +}
> +
> static int release(struct uio_info *info, struct inode *inode)
> {
> struct uio_pci_generic_dev *gdev = to_uio_pci_generic_dev(info);
> @@ -51,7 +60,9 @@ static int release(struct uio_info *info, struct inode *inode)
> * Note that there's a non-zero chance doing this will wedge the device
> * at least until reset.
> */
> - pci_clear_master(gdev->pdev);
> + if (atomic_dec_and_test(&gdev->refcnt))
> + pci_clear_master(gdev->pdev);
> +
> return 0;
> }
>
> @@ -92,8 +103,11 @@ static int probe(struct pci_dev *pdev,
>
> gdev->info.name = "uio_pci_generic";
> gdev->info.version = DRIVER_VERSION;
> + gdev->info.open = open;
> gdev->info.release = release;
> gdev->pdev = pdev;
> + atomic_set(&gdev->refcnt, 0);
> +
> if (pdev->irq && (pdev->irq != IRQ_NOTCONNECTED)) {
> gdev->info.irq = pdev->irq;
> gdev->info.irq_flags = IRQF_SHARED;
> --
> 1.8.3.1
next prev parent reply other threads:[~2022-03-31 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 2:23 [PATCH RESEND] uio/uio_pci_generic: Introduce refcnt on open/release Yao Hongbo
2022-03-31 3:26 ` Joseph Qi
2022-03-31 20:30 ` Michael S. Tsirkin [this message]
2022-04-01 3:23 ` Yao Hongbo
2022-04-01 3:26 ` guanghui.fgh
2022-04-01 5:33 ` Michael S. Tsirkin
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=20220331162952-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alikernel-developer@linux.alibaba.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yaohongbo@linux.alibaba.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).