From: Greg KH <gregkh@linuxfoundation.org>
To: David Lechner <david@lechnology.com>
Cc: linux-iio@vger.kernel.org,
William Breathitt Gray <vilhelm.gray@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] counter: drop chrdev_lock
Date: Mon, 18 Oct 2021 08:08:21 +0200 [thread overview]
Message-ID: <YW0PVYT/GCKAnjN9@kroah.com> (raw)
In-Reply-To: <20211017185521.3468640-1-david@lechnology.com>
On Sun, Oct 17, 2021 at 01:55:21PM -0500, David Lechner wrote:
> This removes the chrdev_lock from the counter subsystem. This was
> intended to prevent opening the chrdev more than once. However, this
> doesn't work in practice since userspace can duplicate file descriptors
> and pass file descriptors to other processes. Since this protection
> can't be relied on, it is best to just remove it.
Much better, thanks!
One remaining question:
> --- a/include/linux/counter.h
> +++ b/include/linux/counter.h
> @@ -297,7 +297,6 @@ struct counter_ops {
> * @events: queue of detected Counter events
> * @events_wait: wait queue to allow blocking reads of Counter events
> * @events_lock: lock to protect Counter events queue read operations
> - * @chrdev_lock: lock to limit chrdev to a single open at a time
> * @ops_exist_lock: lock to prevent use during removal
Why do you still need 2 locks for the same structure?
thanks,
greg k-h
next prev parent reply other threads:[~2021-10-18 6:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 18:55 David Lechner
2021-10-18 6:08 ` Greg KH [this message]
2021-10-18 8:58 ` William Breathitt Gray
2021-10-18 9:13 ` Greg KH
2021-10-18 9:51 ` William Breathitt Gray
2021-10-18 16:14 ` David Lechner
2021-10-18 23:56 ` William Breathitt Gray
2021-10-18 9:14 ` William Breathitt Gray
2021-10-18 16:03 ` David Lechner
2021-10-19 6:53 ` William Breathitt Gray
2021-10-19 7:07 ` Greg KH
2021-10-19 7:18 ` William Breathitt Gray
2021-10-19 7:29 ` Greg KH
2021-10-19 7:46 ` William Breathitt Gray
2021-10-19 9:36 ` Greg KH
2021-10-19 14:44 ` David Lechner
2021-10-19 20:59 ` William Breathitt Gray
2021-10-20 5:42 ` William Breathitt Gray
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=YW0PVYT/GCKAnjN9@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=david@lechnology.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vilhelm.gray@gmail.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®