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: Sat, 5 Dec 2015 08:36:22 -0800 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: Andy Shevchenko <andy.shevchenko@...il.com> Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, "Rafael J . Wysocki" <rjw@...ysocki.net>, "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>, Vinod Koul <vinod.koul@...el.com>, dmaengine <dmaengine@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, Jarkko Nikula <jarkko.nikula@...ux.intel.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Mika Westerberg <mika.westerberg@...ux.intel.com> Subject: Re: [PATCH v3 1/9] device core: add BUS_NOTIFY_DRIVER_NOT_BOUND notification On Sat, Dec 05, 2015 at 06:24:05PM +0200, Andy Shevchenko wrote: > On Sat, Dec 5, 2015 at 6:14 PM, Greg Kroah-Hartman > <gregkh@...uxfoundation.org> wrote: > > On Fri, Dec 04, 2015 at 11:49:17PM +0200, Andy Shevchenko wrote: > >> The users of BUS_NOTIFY_BIND_DRIVER have no chance to do any cleanup in case of > >> a probe failure. In the result there might be problems, such as some resources > >> that had been allocated will continue to be allocated and therefore lead to a > >> resource leak. > >> > >> Introduce a new notification to inform the subscriber that ->probe() failed. Do > >> the same in case of failed device_bind_driver() call. > > > > Ugh, I hate all these notifiers, but this one does make sense... > > Yeah, I'm not a fan of them either. > > > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org> > > You meant Acked-by, didn't you? Either works :) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists