| 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: Fri, 30 Aug 2013 19:06:18 +0200 From: Sascha Hauer <s.hauer@...gutronix.de> To: Fabio Estevam <festevam@...il.com> Cc: Fabio Estevam <fabio.estevam@...escale.com>, Dave Airlie <airlied@...hat.com>, daniel.vetter@...ll.ch, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v2] imx-drm: Fix probe failure On Fri, Aug 30, 2013 at 01:08:14PM -0300, Fabio Estevam wrote: > Hi Sascha, > > On Thu, Aug 29, 2013 at 3:37 PM, Sascha Hauer <s.hauer@...gutronix.de> wrote: > > It's not about the module refcount. It's only that a on a drm device > > which is in use you better do not add/remove components. > > > > Again: The imx-drm driver does *not* do hotplugging. It will *not* add > > or remove components when the device is opened. The code you remove > > exactly makes (or made before Daniels patch) that sure. > > I am not sure what would be the correct fix for this. Why not use (struct drm_device)->open_count as suggested earlier? Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- 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