From: David Lechner <dlechner@baylibre.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Cc: Erick Archer <erick.archer@outlook.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] Input: db9 - use guard notation when acquiring mutex
Date: Wed, 20 Nov 2024 12:33:36 -0600 [thread overview]
Message-ID: <47ea20d8-444b-4c72-97d3-b04a6918b121@baylibre.com> (raw)
In-Reply-To: <20240904043104.1030257-2-dmitry.torokhov@gmail.com>
On 9/3/24 11:30 PM, Dmitry Torokhov wrote:
> Using guard notation makes the code more compact and error handling
> more robust by ensuring that mutexes are released in all code paths
> when control leaves critical section.
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
> drivers/input/joystick/db9.c | 30 ++++++++++++++----------------
> 1 file changed, 14 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/input/joystick/db9.c b/drivers/input/joystick/db9.c
> index 682a29c27832..7ac0cfc3e786 100644
> --- a/drivers/input/joystick/db9.c
> +++ b/drivers/input/joystick/db9.c
> @@ -505,24 +505,22 @@ static int db9_open(struct input_dev *dev)
> {
> struct db9 *db9 = input_get_drvdata(dev);
> struct parport *port = db9->pd->port;
> - int err;
>
> - err = mutex_lock_interruptible(&db9->mutex);
> - if (err)
> - return err;
> -
> - if (!db9->used++) {
> - parport_claim(db9->pd);
> - parport_write_data(port, 0xff);
> - if (db9_modes[db9->mode].reverse) {
> - parport_data_reverse(port);
> - parport_write_control(port, DB9_NORMAL);
> + scoped_guard(mutex_intr, &db9->mutex) {
> + if (!db9->used++) {
> + parport_claim(db9->pd);
> + parport_write_data(port, 0xff);
> + if (db9_modes[db9->mode].reverse) {
> + parport_data_reverse(port);
> + parport_write_control(port, DB9_NORMAL);
> + }
> + mod_timer(&db9->timer, jiffies + DB9_REFRESH_TIME);
> }
> - mod_timer(&db9->timer, jiffies + DB9_REFRESH_TIME);
> +
> + return 0;
> }
>
> - mutex_unlock(&db9->mutex);
> - return 0;
> + return -EINTR;
This patch and any others like it are potentially introducing a bug.
From inspecting the source code, it looks like
mutex_lock_interruptible() can return -EINTR, -EALREADY, or -EDEADLK.
Before this patch, the return value of mutex_lock_interruptible() was
passed to the caller. Now, the return value is reduced to pass/fail
and only -EINTR is returned on failure when the reason could have
been something else.
next prev parent reply other threads:[~2024-11-20 18:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 4:30 [PATCH 0/6] Convert joystick drivers to use new cleanup facilities Dmitry Torokhov
2024-09-04 4:30 ` [PATCH 1/6] Input: db9 - use guard notation when acquiring mutex Dmitry Torokhov
2024-11-20 18:33 ` David Lechner [this message]
2024-11-21 3:52 ` Dmitry Torokhov
2024-09-04 4:30 ` [PATCH 2/6] Input: gamecon " Dmitry Torokhov
2024-09-04 4:31 ` [PATCH 3/6] Input: iforce - use guard notation when acquiring mutex and spinlock Dmitry Torokhov
2024-09-04 4:31 ` [PATCH 4/6] Input: n64joy - use guard notation when acquiring mutex Dmitry Torokhov
2024-09-04 4:31 ` [PATCH 5/6] Input: turbografx " Dmitry Torokhov
2024-09-04 4:31 ` [PATCH 6/6] Input: xpad - use guard notation when acquiring mutex and spinlock Dmitry Torokhov
2024-09-04 4:43 ` [PATCH 0/6] Convert joystick drivers to use new cleanup facilities Dmitry Torokhov
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=47ea20d8-444b-4c72-97d3-b04a6918b121@baylibre.com \
--to=dlechner@baylibre.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=erick.archer@outlook.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®