From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Binoy Jayan <binoy.jayan@linaro.org>,
linux-input@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rajendra <rnayak@codeaurora.org>, Mark Brown <broonie@kernel.org>,
Jiri Kosina <jikos@kernel.org>,
David Herrmann <dh.herrmann@googlemail.com>,
Andrew de los Reyes <adlr@chromium.org>
Subject: Re: [PATCH v2] HID: Replace semaphore driver_lock with mutex
Date: Tue, 13 Jun 2017 11:56:18 +0200 [thread overview]
Message-ID: <20170613095618.GB29589@mail.corp.redhat.com> (raw)
In-Reply-To: <CAK8P3a27bGLpisra1YDT7VntWByk6oS0Fz3e2E0-Nmf-6pVYCA@mail.gmail.com>
Hi,
On Jun 13 2017 or thereabouts, Arnd Bergmann wrote:
> On Tue, Jun 13, 2017 at 11:25 AM, Binoy Jayan <binoy.jayan@linaro.org> wrote:
> > The semaphore 'driver_lock' is used as a simple mutex, and
> > also unnecessary as suggested by Arnd. Hence removing it, as
> > the concurrency between the probe and remove is already
> > handled in the driver core.
> >
> > Signed-off-by: Binoy Jayan <binoy.jayan@linaro.org>
> > Suggested-by: Arnd Bergmann <arnd@arndb.de>
>
> Looks good to me, but I see you didn't include David and Andrew on
> Cc, it would be good for at least one of them to provide an Ack as well.
Please also CC linux-input@
>
> quoting the entire patch for reference, one more comment below:
>
As stated by Arnd in v1, this semaphore only protects probe/removed from
being called concurrently on the same device. And as Arnd said, the
driver model should prevent this to ever happen.
So Acked-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
(one more nitpick below too)
> > ---
> >
> > v1 --> v2
> >
> > Removed driver_lock
> >
> > drivers/hid/hid-core.c | 15 ++++-----------
> > include/linux/hid.h | 2 +-
> > 2 files changed, 5 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
> > index 04cee65..559533b 100644
> > --- a/drivers/hid/hid-core.c
> > +++ b/drivers/hid/hid-core.c
> > @@ -2225,11 +2225,9 @@ static int hid_device_probe(struct device *dev)
> > const struct hid_device_id *id;
> > int ret = 0;
> >
> > - if (down_interruptible(&hdev->driver_lock))
> > - return -EINTR;
> > if (down_interruptible(&hdev->driver_input_lock)) {
> > ret = -EINTR;
> > - goto unlock_driver_lock;
> > + goto end;
> > }
> > hdev->io_started = false;
> >
> > @@ -2256,8 +2254,7 @@ static int hid_device_probe(struct device *dev)
> > unlock:
> > if (!hdev->io_started)
> > up(&hdev->driver_input_lock);
> > -unlock_driver_lock:
> > - up(&hdev->driver_lock);
> > +end:
> > return ret;
> > }
> >
> > @@ -2267,11 +2264,9 @@ static int hid_device_remove(struct device *dev)
> > struct hid_driver *hdrv;
> > int ret = 0;
> >
> > - if (down_interruptible(&hdev->driver_lock))
> > - return -EINTR;
> > if (down_interruptible(&hdev->driver_input_lock)) {
> > ret = -EINTR;
> > - goto unlock_driver_lock;
> > + goto end;
> > }
> > hdev->io_started = false;
> >
> > @@ -2287,8 +2282,7 @@ static int hid_device_remove(struct device *dev)
> >
> > if (!hdev->io_started)
> > up(&hdev->driver_input_lock);
> > -unlock_driver_lock:
> > - up(&hdev->driver_lock);
> > +end:
> > return ret;
> > }
> >
> > @@ -2745,7 +2739,6 @@ struct hid_device *hid_allocate_device(void)
> > init_waitqueue_head(&hdev->debug_wait);
> > INIT_LIST_HEAD(&hdev->debug_list);
> > spin_lock_init(&hdev->debug_list_lock);
> > - sema_init(&hdev->driver_lock, 1);
> > sema_init(&hdev->driver_input_lock, 1);
> >
> > return hdev;
> > diff --git a/include/linux/hid.h b/include/linux/hid.h
> > index 5be325d..1add2b3 100644
> > --- a/include/linux/hid.h
> > +++ b/include/linux/hid.h
> > @@ -516,7 +516,7 @@ struct hid_device { /* device report descriptor */
> > struct hid_report_enum report_enum[HID_REPORT_TYPES];
> > struct work_struct led_work; /* delayed LED worker */
> >
A little bit below, there is:
bool io_started; /* Protected by driver_lock. If IO has started */
You should probably remove the mention to driver_lock here.
> > - struct semaphore driver_lock; /* protects the current driver, except during input */
> > + struct mutex driver_lock; /* protects the current driver, except during input */
> > struct semaphore driver_input_lock; /* protects the current driver */
Unless I am mistaken, this one could also be converted to a mutex (in a
separate patch, of course).
Cheers,
Benjamin
> > struct device dev; /* device */
> > struct hid_driver *driver;
>
> You forgot to actually drop the definition.
>
> Arnd
next parent reply other threads:[~2017-06-13 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1497345926-3262-1-git-send-email-binoy.jayan@linaro.org>
[not found] ` <CAK8P3a27bGLpisra1YDT7VntWByk6oS0Fz3e2E0-Nmf-6pVYCA@mail.gmail.com>
2017-06-13 9:56 ` Benjamin Tissoires [this message]
2017-06-13 10:09 ` [PATCH v2] HID: Replace semaphore driver_lock with mutex Binoy Jayan
2017-06-13 20:00 ` Arnd Bergmann
2017-06-13 15:43 ` David Herrmann
2017-06-13 20:25 ` Arnd Bergmann
2017-06-14 5:22 ` Binoy Jayan
2017-06-14 7:20 ` Arnd Bergmann
2017-06-14 7:45 ` David Herrmann
2017-06-14 11:58 ` Arnd Bergmann
2017-06-19 10:20 ` David Herrmann
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=20170613095618.GB29589@mail.corp.redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=adlr@chromium.org \
--cc=arnd@arndb.de \
--cc=binoy.jayan@linaro.org \
--cc=broonie@kernel.org \
--cc=dh.herrmann@googlemail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rnayak@codeaurora.org \
/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).