From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: radu.sabau@analog.com
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Nuno Sa <nuno.sa@analog.com>, Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Robert Budai <robert.budai@analog.com>,
Antoniu Miclaus <antoniu.miclaus@analog.com>,
Ramona Gradinariu <ramona.gradinariu@analog.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: imu: adis: Fix NULL pointer dereference in adis_init
Date: Fri, 20 Feb 2026 16:06:05 +0200 [thread overview]
Message-ID: <aZhqTRQTLwcdSMkF@smile.fi.intel.com> (raw)
In-Reply-To: <20260220-adis-fix-v1-1-9fa10cce812f@analog.com>
On Fri, Feb 20, 2026 at 03:36:17PM +0200, Radu Sabau via B4 Relay wrote:
> The adis_init() function dereferences adis->ops to check if the
> individual function pointers (write, read, reset) are NULL, but does
> not first check if adis->ops itself is NULL.
>
> Drivers like adis16480, adis16490, adis16545 and others do not set
> custom ops and rely on adis_init() assigning the defaults. Since struct
> adis is zero-initialized by devm_iio_device_alloc(), adis->ops is NULL
> when adis_init() is called, causing a NULL pointer dereference:
>
> Unable to handle kernel NULL pointer dereference at virtual
> address 0000000000000000
No need to wrap backtrace lines. It makes harder to understand the trace.
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
> pc : adis_init+0xc0/0x118
> Call trace:
> adis_init+0xc0/0x118
> adis16480_probe+0xe0/0x670
>
> Fix this by checking if adis->ops is NULL before dereferencing it,
> falling through to assign the default ops in that case.
...
> - if (!adis->ops->write && !adis->ops->read && !adis->ops->reset)
> + if (!adis->ops || (!adis->ops->write && !adis->ops->read && !adis->ops->reset))
> adis->ops = &adis_default_ops;
> else if (!adis->ops->write || !adis->ops->read || !adis->ops->reset)
> return -EINVAL;
Personally I wouldn't mix these two, and do rather
if (!adis->ops)
adis->ops = &adis_default_ops;
// Actually the below check seems redundant to me, I would rather
// expect that be absent in the first place.
else if (!adis->ops->write && !adis->ops->read && !adis->ops->reset)
adis->ops = &adis_default_ops;
else if (!adis->ops->write || !adis->ops->read || !adis->ops->reset)
return -EINVAL;
It also adds a flexibility to only cover missed callbacks in the future
(in case if we need that). But also see above comment.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-20 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 13:36 [PATCH] iio: imu: adis: Fix NULL pointer dereference in adis_init Radu Sabau via B4 Relay
2026-02-20 14:06 ` Andy Shevchenko [this message]
2026-02-20 14:10 ` Miclaus, Antoniu
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=aZhqTRQTLwcdSMkF@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=radu.sabau@analog.com \
--cc=ramona.gradinariu@analog.com \
--cc=robert.budai@analog.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