From: Dmitry Osipenko <digetx@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Takashi Iwai <tiwai@suse.de>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Input: elants_i2c - Fix NULL dereference at probing
Date: Wed, 26 May 2021 23:44:59 +0300 [thread overview]
Message-ID: <b7fc167b-23c6-fd64-cfbf-dd16a90fbf63@gmail.com> (raw)
In-Reply-To: <YK6tZy3E/XZpOAbh@google.com>
Hello all,
26.05.2021 23:19, Dmitry Torokhov пишет:
> Hi Takashi,
>
> On Wed, May 26, 2021 at 09:43:01PM +0200, Takashi Iwai wrote:
>> The recent change in elants_i2c driver to support more chips
>> introduced a regression leading to Oops at probing. The driver reads
>> id->driver_data, but the id may be NULL depending on the device type
>> the driver gets bound.
>>
>> Add a NULL check and falls back to the default EKTH3500.
>
> Thank you for the patch. I think my preference would be to switch to
> device_get_match_data() and annotate the rest of the match tables with
> proper controller types.
Doesn't a NULL mean that elants_i2c_id[] table fails to match the ACPI
device name? What is the name then?
This could be two patches:
1 - trivial fix that can be backported easily
2 - switch to device_get_match_data()
next prev parent reply other threads:[~2021-05-26 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 19:43 [PATCH] Input: elants_i2c - Fix NULL dereference at probing Takashi Iwai
2021-05-26 20:19 ` Dmitry Torokhov
2021-05-26 20:44 ` Dmitry Osipenko [this message]
2021-05-27 6:22 ` Takashi Iwai
2021-05-27 19:01 ` Dmitry Osipenko
2021-05-27 6:20 ` Takashi Iwai
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=b7fc167b-23c6-fd64-cfbf-dd16a90fbf63@gmail.com \
--to=digetx@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
/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).