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
| ||
|
Date: Mon, 1 Jun 2020 16:51:01 +0300 From: Andy Shevchenko <andy.shevchenko@...il.com> To: Johan Hovold <johan@...nel.org> Cc: Jacek Anaszewski <jacek.anaszewski@...il.com>, Pavel Machek <pavel@....cz>, Dan Murphy <dmurphy@...com>, Amitoj Kaur Chawla <amitoj1606@...il.com>, Linux LED Subsystem <linux-leds@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 0/6] leds: fix broken devres usage On Mon, Jun 1, 2020 at 4:42 PM Johan Hovold <johan@...nel.org> wrote: > > Several MFD child drivers register their class devices directly under > the parent device (about half of the MFD LED drivers do so). > > This means you cannot blindly do devres conversions so that > deregistration ends up being tied to the parent device, something which > leads to use-after-free on driver unbind when the class device is > released while still being registered (and, for example, oopses on later > parent MFD driver unbind or LED class callbacks, or resource leaks and > name clashes on child driver reload). Shouldn't MFD take reference count for their children? -- With Best Regards, Andy Shevchenko
Powered by blists - more mailing lists