From: Greg KH <gregkh@linuxfoundation.org>
To: Oded Gabbay <oded.gabbay@gmail.com>
Cc: linux-kernel@vger.kernel.org, oshpigelman@habana.ai, ttayar@habana.ai
Subject: Re: [PATCH] habanalabs: use correct variable to show fd open counter
Date: Mon, 8 Jul 2019 13:21:36 +0200 [thread overview]
Message-ID: <20190708112136.GA13795@kroah.com> (raw)
In-Reply-To: <20190708104355.32569-1-oded.gabbay@gmail.com>
On Mon, Jul 08, 2019 at 01:43:55PM +0300, Oded Gabbay wrote:
> The current code checks if the user context pointer is NULL or not to
> display the number of open file descriptors of a device. However, that
> variable (user_ctx) will eventually go away as the driver will support
> multiple processes. Instead, the driver can use the atomic counter of
> the open file descriptors which the driver already maintains.
>
> Signed-off-by: Oded Gabbay <oded.gabbay@gmail.com>
> ---
> drivers/misc/habanalabs/sysfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/misc/habanalabs/sysfs.c b/drivers/misc/habanalabs/sysfs.c
> index 25eb46d29d88..881be19b5fad 100644
> --- a/drivers/misc/habanalabs/sysfs.c
> +++ b/drivers/misc/habanalabs/sysfs.c
> @@ -356,7 +356,7 @@ static ssize_t write_open_cnt_show(struct device *dev,
> {
> struct hl_device *hdev = dev_get_drvdata(dev);
>
> - return sprintf(buf, "%d\n", hdev->user_ctx ? 1 : 0);
> + return sprintf(buf, "%d\n", atomic_read(&hdev->fd_open_cnt));
> }
Odds are, this means nothing, as it doesn't get touched if the file
descriptor is duped or sent to another process.
Why do you care about the number of open files? Whenever someone tries
to do this type of logic, it is almost always wrong, just let userspace
do what it wants to do, and if wants to open something twice, then it
gets to keep the pieces when things break.
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-08 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 10:43 [PATCH] habanalabs: use correct variable to show fd open counter Oded Gabbay
2019-07-08 11:08 ` Tomer Tayar
2019-07-08 11:21 ` Greg KH [this message]
2019-07-08 11:30 ` Oded Gabbay
2019-07-08 11:37 ` Oded Gabbay
2019-07-08 12:21 ` Greg KH
2019-07-08 11:42 ` Greg KH
2019-07-08 11:51 ` Oded Gabbay
2019-07-08 12:20 ` Greg KH
2019-07-08 14:28 ` Oded Gabbay
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=20190708112136.GA13795@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.com \
--cc=oshpigelman@habana.ai \
--cc=ttayar@habana.ai \
/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