linux-kernel - Re: LED subsystem lagging maintenance

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 28 Jul 2021 14:31:43 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Pavel Machek <pavel@....cz>
Cc:     Linux LED Subsystem <linux-leds@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        Hans de Goede <hdegoede@...hat.com>,
        Pavel Machek <pavel@...x.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: LED subsystem lagging maintenance

On Wed, Jul 28, 2021 at 2:17 PM Pavel Machek <pavel@....cz> wrote:

...

> > > To be honest, patches were not applied because they were not that
> > > important to begin with,
> >
> > Reference counting disbalance is not critical, but what is then?
>
> Things with end-user impact. What is end-user impact here? How much
> memory is leaked in usual config?

Not sure what "usual" means, but if the user has a device in question,
then it's struct fwnode_handle (7 pointers + u8, unpacked) per each
modprobe. Taking into account that there are usually not so many of
the same LED devices in the system  and the user rarely does
rmmod/insmod cycle, I can say a few dozens of bytes.


-- 
With Best Regards,
Andy Shevchenko