From: "Mårten Lindahl" <martenli@axis.com>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Mårten Lindahl" <marten.lindahl@axis.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>, <linux-iio@vger.kernel.org>,
<kernel@axis.com>
Subject: Re: [PATCH v2] iio: light: vcnl4000: Fix WARN_ON on uninitialized lock
Date: Tue, 31 Jan 2023 14:27:51 +0100 [thread overview]
Message-ID: <67f7888c-5d5b-4c63-42d3-cf2b15602478@axis.com> (raw)
In-Reply-To: <Y9kKsv7OJ1KoImjJ@smile.fi.intel.com>
On 1/31/23 13:33, Andy Shevchenko wrote:
> On Tue, Jan 31, 2023 at 11:29:51AM +0100, Mårten Lindahl wrote:
>> There are different init functions for the sensors in this driver in
>> which only one initialize the generic vcnl4000_lock. With commit
> initializes ?
>
>> e21b5b1f2669 ("iio: light: vcnl4000: Preserve conf bits when toggle power")
>> the vcnl4040 sensor started to depend on the lock, but it was missed to
>> initialize it in vcnl4040's init function. This has not been visible
>> until we run lockdep on it:
>>
>> DEBUG_LOCKS_WARN_ON(lock->magic != lock)
>> at kernel/locking/mutex.c:575 __mutex_lock+0x4f8/0x890
>> Call trace:
>> __mutex_lock
>> mutex_lock_nested
>> vcnl4200_set_power_state
>> vcnl4200_init
>> vcnl4000_probe
>> i2c_device_probe
>> really_probe
>> __driver_probe_device
>> driver_probe_device
>> __driver_attach
>> bus_for_each_dev
>> driver_attach
>> bus_add_driver
>> driver_register
>> i2c_register_driver
>> vcnl4000_driver_init
> E.g. the following can be cut without losing significance of the data
> (see below as well).
>
>> do_one_initcall
>> do_init_module
>> load_module
>> __do_sys_finit_module
>> Fix this by initializing the lock in the probe function instead of doing
>> it in the chip specific init functions.
>>
>> Fixes: e21b5b1f2669 ("iio: light: vcnl4000: Preserve conf bits when toggle power")
>> Signed-off-by: Mårten Lindahl <marten.lindahl@axis.com>
>> ---
>>
>> v2:
>> - Trimmed backtrace in commit message
> Not enough, please try harder. The ideal is to have ~3-5 lines of traceback.
Hi Andy, Maybe I get it right soon ;). Could it perhaps be stripped like
this?
Call trace:
__mutex_lock
mutex_lock_nested
vcnl4200_set_power_state
vcnl4200_init
vcnl4000_probe
i2c_device_probe
Kind regards
Mårten
>
>> - Have 12 digit sha-1 id in Fixes tag
>> - Make the lock initialization in probe instead of in _init function
> ...
>
>> data->client = client;
>> data->id = id->driver_data;
>> data->chip_spec = &vcnl4000_chip_spec_cfg[data->id];
> + Blank line.
>
>> + mutex_init(&data->vcnl4000_lock);
>>
>> ret = data->chip_spec->init(data);
>> if (ret < 0)
next prev parent reply other threads:[~2023-01-31 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 10:29 [PATCH v2] iio: light: vcnl4000: Fix WARN_ON on uninitialized lock Mårten Lindahl
2023-01-31 12:33 ` Andy Shevchenko
2023-01-31 12:37 ` Andy Shevchenko
2023-01-31 13:27 ` Mårten Lindahl [this message]
2023-01-31 13:37 ` Andy Shevchenko
2023-01-31 13:42 ` Mårten Lindahl
2023-01-31 12:46 ` Cai Huoqing
2023-01-31 13:33 ` Mårten Lindahl
2023-01-31 13:36 ` Andy Shevchenko
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=67f7888c-5d5b-4c63-42d3-cf2b15602478@axis.com \
--to=martenli@axis.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jic23@kernel.org \
--cc=kernel@axis.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=marten.lindahl@axis.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