From: sashiko-bot@kernel.org
To: "Rosen Penev" <rosenp@gmail.com>, linux-leds@vger.kernel.org
Cc: lee@kernel.org
Subject: Re: [PATCH v3] leds: is31fl32xx: Fix NULL pointer dereference when binding via I2C ID table
Date: Sun, 18 Oct 2026 22:52:11 +0000 [thread overview]
Message-ID: <sashiko-outbox-176435@kernel.org> (raw)
In-Reply-To: <20261018225036.12000-1-rosenp@gmail.com>
> If the device binds via the I2C ID table (e.g. sysfs new_device, a
> software node, or a firmware node without a matching compatible),
> device_get_match_data() in is31fl32xx_probe() returns NULL, since only
> the OF match table carries the chip definition. is31fl32xx_parse_dt()
> then dereferences cdef->output_frequency_setting_reg and
> is31fl32xx_parse_child_dt() dereferences cdef->channels, causing a
> kernel oops.
>
> Populate .driver_data in is31fl32xx_id with the same chip definitions
> as the OF table and use i2c_get_match_data(), which falls back to the
> I2C ID table when no firmware match data is available. Every entry
> now carries match data, so cdef can no longer be NULL.
>
> Drop the comment above the ID table, as the table is now used for
> matching data as well.
>
> Fixes: 2779f4724b2f ("leds: various: use device_get_match_data")
> Cc: stable@vger.kernel.org
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261018225036.12000-1-rosenp@gmail.com?part=1
prev parent reply other threads:[~2026-10-18 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 22:50 [PATCH v3] leds: is31fl32xx: Fix NULL pointer dereference when binding via I2C ID table Rosen Penev
2026-10-18 22:52 ` sashiko-bot [this message]
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=sashiko-outbox-176435@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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