Re: [PATCH] drivers-core: nullify private pointer on device-release

From: Greg KH
Date: Mon Oct 05 2009 - 12:07:50 EST


On Mon, Oct 05, 2009 at 10:11:50AM +0200, Guennadi Liakhovetski wrote:
> On Thu, 1 Oct 2009, Greg KH wrote:
>
> > On Thu, Oct 01, 2009 at 03:45:56PM +0200, Guennadi Liakhovetski wrote:
> > > On Thu, 1 Oct 2009, Greg KH wrote:
> > >
> > > > On Thu, Oct 01, 2009 at 10:02:08AM +0200, Guennadi Liakhovetski wrote:
> > > > > Device structures can be reused over multiple device_add / device_release
> > > > > cycles.
> > > >
> > > > They shouldn't be as they should be dynamic, not static.
> > >
> > > Should they? I'm pretty sure this is not the first time this comes up -
> > > there are several drivers and / or subsystems, that re-use driver objects.
> >
> > Then those drivers and subsystems should be fixed, as that is incorrect.
> >
> > > But finding in mail archives wouldn't be very easy. And it worked until
> > > now - why should we break it?
> >
> > I would argue that this code was always broken.
> > When did this problem show up for you?
>
> Since commit b4028437876866aba4747a655ede00f892089e14

Again, which driver/devices are having this problem? The patch
referenced above had been in linux-next for almost 6 months with no
reported problems, so this is news to me :)

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/