Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: "Mårten Lindahl" <martenli@axis.com>
Cc: "Mårten Lindahl" <marten.lindahl@axis.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	linux-iio@vger.kernel.org, kernel@axis.com
Subject: Re: [PATCH] iio: light: vcnl4000: Fix WARN_ON on uninitialized lock
Date: Mon, 30 Jan 2023 17:30:29 +0000	[thread overview]
Message-ID: <20230130173029.00006995@huawei.com> (raw)
In-Reply-To: <6a1d8766-2777-83d6-6d1f-ecb81da4b11a@axis.com>

On Mon, 30 Jan 2023 15:10:40 +0100
Mårten Lindahl <martenli@axis.com> wrote:

> On 1/30/23 14:04, Jonathan Cameron wrote:
> > On Mon, 30 Jan 2023 10:37:42 +0100
> > Mårten Lindahl <marten.lindahl@axis.com> wrote:
> >  
> >> There are different init functions for the sensors in this driver in
> >> which only one initialize the generic vcnl4000_lock. With commit
> >> e21b5b1f2 ("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)
> >>    WARNING: CPU: 1 PID: 8800 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
> >>     do_one_initcall
> >>     do_init_module
> >>     load_module
> >>     __do_sys_finit_module
> >>     ...
> >>
> >> Fix this by adding mutex_init on the lock in the init function used for
> >> vcnl4040.
> >>
> >> Fixes: e21b5b1f2 ("iio: light: vcnl4000: Preserve conf bits when toggle power")
> >> Signed-off-by: Mårten Lindahl <marten.lindahl@axis.com>  
> > Perhaps better to pull the lock out of the device specific setup?  
> 
> Hi Jonathan!
> 
> Ok, having a
> 
> static DEFINE_MUTEX(vcnl4000_lock);
> 
No. Definitely don't do that.  We need one per device instance.

I just meant move the mutex_init() into the main probe function rather
than the chip specific init that is called from there.

> will make sure initializing it wont be forgotten for specific setups.
> 
> I'll test it.
> 
> Kind regards
> 
> Mårten
> 
> >  
> >> ---
> >>   drivers/iio/light/vcnl4000.c | 1 +
> >>   1 file changed, 1 insertion(+)
> >>
> >> diff --git a/drivers/iio/light/vcnl4000.c b/drivers/iio/light/vcnl4000.c
> >> index cc1a2062e76d..a8a9fc3b1a02 100644
> >> --- a/drivers/iio/light/vcnl4000.c
> >> +++ b/drivers/iio/light/vcnl4000.c
> >> @@ -316,6 +316,7 @@ static int vcnl4200_init(struct vcnl4000_data *data)
> >>   	}
> >>   	mutex_init(&data->vcnl4200_al.lock);
> >>   	mutex_init(&data->vcnl4200_ps.lock);
> >> +	mutex_init(&data->vcnl4000_lock);
> >>   
> >>   	ret = data->chip_spec->set_power_state(data, true);
> >>   	if (ret < 0)  


  reply	other threads:[~2023-01-30 17:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30  9:37 [PATCH] iio: light: vcnl4000: Fix WARN_ON on uninitialized lock Mårten Lindahl
2023-01-30 12:39 ` Andy Shevchenko
2023-01-30 12:40   ` Andy Shevchenko
2023-01-30 14:05     ` Mårten Lindahl
2023-01-30 13:04 ` Jonathan Cameron
2023-01-30 14:10   ` Mårten Lindahl
2023-01-30 17:30     ` Jonathan Cameron [this message]
2023-01-31  7:49       ` Mårten Lindahl

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=20230130173029.00006995@huawei.com \
    --to=jonathan.cameron@huawei.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 \
    --cc=martenli@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