From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jason Gerecke <killertofu@gmail.com>
Cc: jkosina@suse.cz, benjamin.tissoires@gmail.com,
pinglinux@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] HID: wacom: Prevent potential null dereference after disconnect
Date: Wed, 8 Oct 2014 14:40:45 -0700 [thread overview]
Message-ID: <20141008214045.GF15198@dtor-ws> (raw)
In-Reply-To: <1412792742-4075-1-git-send-email-killertofu@gmail.com>
On Wed, Oct 08, 2014 at 11:25:42AM -0700, Jason Gerecke wrote:
> Repeated connect/disconnect cycles under GNOME can trigger an occasional
> OOPS from within e.g. wacom_led_select_store, presumably due to a timing
> issue where userspace begins setting a value immediately before the
> device disconnects and our shared data is whisked away.
>
> Signed-off-by: Jason Gerecke <killertofu@gmail.com>
> ---
> Changes in v2:
> * Added in missing escape character
>
> drivers/hid/wacom_sys.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/hid/wacom_sys.c b/drivers/hid/wacom_sys.c
> index 8593047..265429b 100644
> --- a/drivers/hid/wacom_sys.c
> +++ b/drivers/hid/wacom_sys.c
> @@ -641,6 +641,9 @@ static ssize_t wacom_led_select_store(struct device *dev, int set_id,
> unsigned int id;
> int err;
>
> + if (!wacom)
> + return -ENODEV;
> +
Strong NAK. If device could disappear before this check it could as well
disappear after your check.
This patch does not solve anything.
> err = kstrtouint(buf, 10, &id);
> if (err)
> return err;
Thanks.
--
Dmitry
next prev parent reply other threads:[~2014-10-08 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 17:54 [PATCH] HID: wacom: Prevent potential null dereference after disconnect Jason Gerecke
2014-10-08 18:25 ` [PATCH v2] " Jason Gerecke
2014-10-08 21:40 ` Dmitry Torokhov [this message]
2014-10-09 0:24 ` Jason Gerecke
2014-10-09 0:28 ` Dmitry Torokhov
2014-10-09 2:08 ` Jason Gerecke
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=20141008214045.GF15198@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@gmail.com \
--cc=jkosina@suse.cz \
--cc=killertofu@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pinglinux@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;
as well as URLs for NNTP newsgroup(s).