From: Herve Codina <herve.codina@bootlin.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Miaoqian Lin <linmq006@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "leds: led-core: Fix refcount leak in of_led_get()"
Date: Tue, 25 Jun 2024 10:07:09 +0200 [thread overview]
Message-ID: <20240625100709.307568fd@bootlin.com> (raw)
In-Reply-To: <20240625-led-class-device-leak-v1-1-9eb4436310c2@bootlin.com>
Hi Luca,
On Tue, 25 Jun 2024 09:26:52 +0200
Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
> This reverts commit da1afe8e6099980fe1e2fd7436dca284af9d3f29.
>
> Commit 699a8c7c4bd3 ("leds: Add of_led_get() and led_put()"), introduced in
> 5.5, added of_led_get() and led_put() but missed a put_device() in
> led_put(), thus creating a leak in case the consumer device is removed.
>
> Arguably device removal was not very popular, so this went apparently
> unnoticed until 2022. In January 2023 two different patches got merged to
> fix the same bug:
>
> - commit da1afe8e6099 ("leds: led-core: Fix refcount leak in of_led_get()")
> - commit 445110941eb9 ("leds: led-class: Add missing put_device() to led_put()")
>
> They fix the bug in two different ways, which creates no patch conflicts,
> and both were merged in v6.2. The result is that now there is one more
> put_device() than get_device()s, instead of one less.
>
> Arguably device removal is not very popular yet, so this apparently hasn't
> been noticed as well up to now. But it blew up here while I'm working with
> device tree overlay insertion and removal. The symptom is an apparently
> unrelated list of oopses on device removal, with reasons:
>
> kernfs: can not remove 'uevent', no directory
> kernfs: can not remove 'brightness', no directory
> kernfs: can not remove 'max_brightness', no directory
> ...
>
> Here sysfs fails removing attribute files, which is because the device name
> changed and so the sysfs path. This is because the device name string got
> corrupted, which is because it got freed too early and its memory reused.
>
> Different symptoms could appear in different use cases.
>
> Fix by removing one of the two fixes.
>
> The choice was to remove commit da1afe8e6099 because:
>
> * it is calling put_device() inside of_led_get() just after getting the
> device, thus it is basically not refcounting the LED device at all
> during its entire lifetime
> * it does not add a corresponding put_device() in led_get(), so it fixes
> only the OF case
>
> The other fix (445110941eb9) is adding the put_device() in led_put() so it
> covers the entire lifetime, and it works even in the non-DT case.
>
> Fixes: da1afe8e6099 ("leds: led-core: Fix refcount leak in of_led_get()")
> Co-developed-by: Hervé Codina <herve.codina@bootlin.com>
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
As there is a Co-developer, you have to add his/her Signed-off-by:
https://elixir.bootlin.com/linux/v6.10-rc5/source/Documentation/process/submitting-patches.rst#L494
So feel free to:
a) Add Signed-off-by: Hervé Codina <herve.codina@bootlin.com>
or
b) Remove Co-developed-by: Hervé Codina <herve.codina@bootlin.com>
Even if I participate in that fix, I will not be upset if you remove the
Co-developed-by :)
Best regards,
Hervé
next prev parent reply other threads:[~2024-06-25 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 7:26 [PATCH] Revert "leds: led-core: Fix refcount leak in of_led_get()" Luca Ceresoli
2024-06-25 8:07 ` Herve Codina [this message]
2024-06-25 8:33 ` Luca Ceresoli
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=20240625100709.307568fd@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=hdegoede@redhat.com \
--cc=lee@kernel.org \
--cc=linmq006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=pavel@ucw.cz \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).