Linux LED subsystem development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lee Jones <lee@kernel.org>
Cc: Myeonghun Pak <mhun512@gmail.com>,
	Jan-Simon Moeller <jansimon.moeller@gmx.de>,
	Pavel Machek <pavel@kernel.org>,
	Joseph Strauss <jstrauss@mailbox.org>,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] leds: blinkm: Clean up sysfs group on LED registration failure
Date: Thu, 15 Oct 2026 14:51:47 +0200	[thread overview]
Message-ID: <2026101556-boxer-underfoot-1e9f@gregkh> (raw)
In-Reply-To: <179198508016.839288.4695468891309561458@kernel.org>

On Thu, Oct 15, 2026 at 12:54:33PM +0100, Lee Jones wrote:
> On Fri, 25 Sep 2026, Myeonghun Pak wrote:
> 
> > blinkm_probe() creates the BlinkM sysfs group before registering the LED
> > class devices. If multicolor sub-LED allocation fails, probe returns
> > without removing the group. If multicolor LED registration fails, the
> > helper removes the group but returns success, leaving the device bound
> > without an LED class device.
> >
> > Keep LED class device rollback in the registration helpers, but remove
> > the BlinkM sysfs group in blinkm_probe() when either registration mode
> > fails. Propagate the multicolor registration error so probe can perform
> > this cleanup and report the failure.
> >
> > Fixes: 56e8c56c9af0 ("leds: Add multicolor support to BlinkM LED driver")
> > Cc: stable@vger.kernel.org
> > Assisted-by: LLM
> > Co-developed-by: Ijae Kim <ae878000@gmail.com>
> > Signed-off-by: Ijae Kim <ae878000@gmail.com>
> > Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
> > ---
> > Changes in v2:
> > - Move sysfs group cleanup to blinkm_probe() for both LED registration modes.
> > - Propagate multicolor LED registration errors to blinkm_probe().
> >
> >  drivers/leds/leds-blinkm.c | 15 ++++++---------
> >  1 file changed, 6 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/leds/leds-blinkm.c b/drivers/leds/leds-blinkm.c
> > --- a/drivers/leds/leds-blinkm.c
> > +++ b/drivers/leds/leds-blinkm.c
> > @@ -671,7 +671,6 @@ failblue:
> >  failgreen:
> >  	led_classdev_unregister(&leds[RED]->cdev.led_cdev);
> >  failred:
> > -	sysfs_remove_group(&client->dev.kobj, &blinkm_group);
> >
> >  	return err;
> >  }
> > @@ -714,9 +713,8 @@ static int register_multicolor(struct i2c_client *client, struct blinkm_data *da
> >  	if (err < 0) {
> >  		dev_err(&client->dev, "couldn't register LED %s\n",
> >  				mc_led->cdev.led_cdev.name);
> > -		sysfs_remove_group(&client->dev.kobj, &blinkm_group);
> >  	}
> > -	return 0;
> > +	return err;
> >  }
> >
> >  static int blinkm_probe(struct i2c_client *client)
> > @@ -749,13 +747,12 @@ static int blinkm_probe(struct i2c_client *client)
> >  	}
> >
> > -	if (!IS_ENABLED(CONFIG_LEDS_BLINKM_MULTICOLOR)) {
> > +	if (!IS_ENABLED(CONFIG_LEDS_BLINKM_MULTICOLOR))
> >  		err = register_separate_colors(client, data);
> > -		if (err < 0)
> > -			return err;
> > -	} else {
> > +	else
> >  		err = register_multicolor(client, data);
> 
> Please add a newline after the 'if-else' block.
> 
> > -		if (err < 0)
> > -			return err;
> > +	if (err < 0) {
> > +		sysfs_remove_group(&client->dev.kobj, &blinkm_group);
> 
> How about using 'devm_device_add_group() to automate clean-up?

Wait, why is a driver manually adding sysfs files at all?  Shouldn't
this "just work" if it's a default group for the driver?  This way (or
with the devm_device_add_group() call) will race with userspace and
loose.

thanks,

greg k-h

      reply	other threads:[~2026-10-15 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26  0:03 [PATCH v2] leds: blinkm: Clean up sysfs group on LED registration failure Myeonghun Pak
2026-09-26  0:12 ` sashiko-bot
2026-10-15 11:54 ` Lee Jones
2026-10-15 12:51   ` Greg KH [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=2026101556-boxer-underfoot-1e9f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jansimon.moeller@gmx.de \
    --cc=jstrauss@mailbox.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mhun512@gmail.com \
    --cc=pavel@kernel.org \
    --cc=stable@vger.kernel.org \
    /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