Re: usb serial driver: private data already deallocated when release function is called

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 7 Jan 2013, Tilman wrote:

> Hello
> 
> I am porting a usb test driver from kernel version 3.0.8 to 
> kernel version 3.7.1. 
> 
> The release function was working on V3.0.0. On V3.7.1, the 
> private data stored in serial->port.device->p->driver_data 
> seems already to be deallocated (or never correctly be 
> allocated): usb_get_serial_port_data returns a null pointer.

There were changes to almost all of the serial drivers in that time
period.  The problem was that they were using their release method to
do work that needed to be done in the port_remove method.

> Is there any function as part of the usb kernel framework 
> that releases the private data before calling the release 
> function ?

Nope, your driver has to do that in its port_remove method.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux