RE: [Xen-devel] Null-pointer access in netback_uevent

["James Harper" <james.harper@xxxxxxxxxxxxxxxx>]

> > > Looking into this further, I suspect that the trigger here is a newer
> > > version of udev or something in that area. netback_uevent is getting 
> > > called
> > > before the call to netback_probe containing the call to dev_set_drvdata.
> > >
> > There are two problems there. And yes, the uevent routine can be called
> > at any time.
> >
> 
> So would it be correct for it to just return if either of those are
> NULL?

Not sure. It works though.

>  Will it get called again later once the device info is available?

It does get called again later when the device info has been populated. I'm not 
sure if we can count on that though.

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel