mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Su Weifeng <suweifeng1@huawei.com>
Cc: mst@redhat.com, linux-kernel@vger.kernel.org,
	shikemeng@huawei.com, liuzhiqiang26@huawei.com,
	linfeilong@huawei.com, zhanghongtao22@huawei.com
Subject: Re: [PATCH v2] uio:uio_pci_generic:Don't clear master bit when the process does not exit
Date: Mon, 20 Feb 2023 19:11:38 +0100	[thread overview]
Message-ID: <Y/O32v/KZt+RjoHQ@kroah.com> (raw)
In-Reply-To: <20230220171045.689736-1-suweifeng1@huawei.com>

On Tue, Feb 21, 2023 at 01:10:44AM +0800, Su Weifeng wrote:
> From: Weifeng Su <suweifeng1@huawei.com>
> 
> The /dev/uioX device has concurrent operations in a few scenarios.
> 
> For example, when a process using the device exits abnormally,
> the management program starts the same process to operate the device.
> When the process exits and closes the /dev/uioX device,
> the master bit of the device is cleared. In this case, if the
> new process is issuing commands, I/Os are suspended and cannot be
> automatically recovered.
> 
> Therefore, reference counting is added to clear the master bit
> only when the last process exits.
> 
> Signed-off-by: Weifeng Su <suweifeng1@huawei.com>
> ---
> The difference between the first patch and the first patch is that 
> the reference counting operation is performed using the atomic semantics, 
> just like other drivers under UIO:
> cdfa835c6e5e87d145f("uio_hv_generic: defer opening vmbus until first use").

And I would claim that that change too is incorrect.

Did you test this with dup()?  Lots of open/close cycles on the same
device node?  Passing around the file descriptor?

Logically, this is identical to your previous change, so why should it
be accepted?

Again, why not just use a real PCI driver for your device?

thanks,

greg k-h

  reply	other threads:[~2023-02-20 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 17:10 Su Weifeng
2023-02-20 18:11 ` Greg KH [this message]
2023-02-21 12:48   ` Weifeng Su
2023-02-23 15:09     ` Weifeng Su

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=Y/O32v/KZt+RjoHQ@kroah.com \
    --to=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=suweifeng1@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®