Message ID | 20231204180603.470421-3-gnstark@salutedevices.com |
---|---|
State | Superseded |
Headers | show |
Series | devm_led_classdev_register() usage problem | expand |
On Mon, Dec 4, 2023 at 8:07 PM George Stark <gnstark@salutedevices.com> wrote: > > In the probe() callback in case of error mutex is destroyed being locked > which is not allowed so unlock the mute before destroying. Sounds to me like this is a real fix, hence the Fixes tag and being first in the series. You free to add Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Le 04/12/2023 à 19:05, George Stark a écrit : > In the probe() callback in case of error mutex is destroyed being locked > which is not allowed so unlock the mute before destroying. Should there be a fixes: tag ? For instance on 59ea3c9faf32 ("leds: add aw2013 driver") ? > > Signed-off-by: George Stark <gnstark@salutedevices.com> > --- > drivers/leds/leds-aw2013.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/leds/leds-aw2013.c b/drivers/leds/leds-aw2013.c > index 59765640b70f..c2bc0782c0cd 100644 > --- a/drivers/leds/leds-aw2013.c > +++ b/drivers/leds/leds-aw2013.c > @@ -397,6 +397,7 @@ static int aw2013_probe(struct i2c_client *client) > regulator_disable(chip->vcc_regulator); > > error: > + mutex_unlock(&chip->mutex); > mutex_destroy(&chip->mutex); > return ret; > }
diff --git a/drivers/leds/leds-aw2013.c b/drivers/leds/leds-aw2013.c index 59765640b70f..c2bc0782c0cd 100644 --- a/drivers/leds/leds-aw2013.c +++ b/drivers/leds/leds-aw2013.c @@ -397,6 +397,7 @@ static int aw2013_probe(struct i2c_client *client) regulator_disable(chip->vcc_regulator); error: + mutex_unlock(&chip->mutex); mutex_destroy(&chip->mutex); return ret; }
In the probe() callback in case of error mutex is destroyed being locked which is not allowed so unlock the mute before destroying. Signed-off-by: George Stark <gnstark@salutedevices.com> --- drivers/leds/leds-aw2013.c | 1 + 1 file changed, 1 insertion(+)