From: "Suweifeng (Weifeng, EulerOS)" <suweifeng1@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <mst@redhat.com>, <linux-kernel@vger.kernel.org>,
<shikemeng@huawei.com>, <liuzhiqiang26@huawei.com>,
<linfeilong@huawei.com>, <zhanghongtao22@huawei.com>
Subject: Re: [PATCH] uio:uio_pci_generic:Don't clear master bit when the process does not exit
Date: Thu, 16 Feb 2023 22:45:02 +0800 [thread overview]
Message-ID: <1601ce95-5ec7-3656-cdcd-bf052cf6d222@huawei.com> (raw)
In-Reply-To: <Y+uJ6ejVNl6RoQPk@kroah.com>
On 2023/2/14 21:17, Greg KH wrote:
> On Tue, Feb 14, 2023 at 09:21:57PM +0800, Su Weifeng wrote:
>> From: Weifeng Su <suweifeng1@huawei.com>
>>
>> The /dev/uioX device is used by multiple processes. The current behavior
>> is to clear the master bit when a process exits. This affects other
>> processes that use the device, resulting in command suspension and
>> timeout. This behavior cannot be sensed by the process itself.
>> The solution is to add the reference counting. The reference count is
>> self-incremented and self-decremented each time when the device open and
>> close. The master bit is cleared only when the last process exited.
>>
>> Signed-off-by: Weifeng Su <suweifeng1@huawei.com>
>> ---
>> drivers/uio/uio_pci_generic.c | 18 +++++++++++++++++-
>> 1 file changed, 17 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/uio/uio_pci_generic.c b/drivers/uio/uio_pci_generic.c
>> index e03f9b532..d36d3e08e 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;
>> + refcount_t dev_refc;
>> };
>>
>> static inline struct uio_pci_generic_dev *
>> @@ -39,10 +40,22 @@ to_uio_pci_generic_dev(struct uio_info *info)
>> 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);
>> +
>> + if (gdev)
>> + refcount_inc(&gdev->dev_refc);
>
> This flat out does not work, sorry.
>
> You should never rely on trying to count open/release calls, just let
> the vfs layer handle that for us as it currently does so.
>
> Think about what happens if you call dup() in userspace on a
> filehandle...
>
>> + return 0;
>> +}
>> +
>> static int release(struct uio_info *info, struct inode *inode)
>> {
>> struct uio_pci_generic_dev *gdev = to_uio_pci_generic_dev(info);
>>
>> + if (gdev && refcount_dec_not_one(&gdev->dev_refc))
>
> I don't think you actually tested this as it is impossible for gdev to
> ever be NULL.
>
> sorry, but this patch is not correct.
>
> greg k-h
First of all, thank you for taking the time to read this patch, your
comments are very enlightening, but I do have a strange problem here, I
test such programs on kernels 5.10 and 6.2.
fd = open("/dev/uio0". O_RDWR);
while (true)
sleep(1);
This program only opens the uio device. After starting multiple such
processes, I close one of them. From the added print, it can be seen
that the "uio_pci_generic.c:release" function is called and the master
bit is cleared, instead of being called when the last process exits as
expected. I think the vfs is not protected as it should be. Such a
problem cannot be handled in the user-mode program. We have to clear the
master bit when the last process exits. Otherwise, user-mode programs
(for example, the DPDK process that uses uio_pci_generic) cannot work
properly.
Best regards,
Weifeng Su
next prev parent reply other threads:[~2023-02-16 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 13:21 Su Weifeng
2023-02-14 13:17 ` Greg KH
2023-02-16 14:45 ` Suweifeng (Weifeng, EulerOS) [this message]
2023-02-16 15:07 ` Greg KH
2023-02-16 15:55 ` Michael S. Tsirkin
2023-02-16 16:57 ` Greg KH
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=1601ce95-5ec7-3656-cdcd-bf052cf6d222@huawei.com \
--to=suweifeng1@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=mst@redhat.com \
--cc=shikemeng@huawei.com \
--cc=zhanghongtao22@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
all inboxes | Powered by JetHome®