"Du, ChangbinX" writes:
>> From: Bjørn Mork [mailto:bj...@mork.no]
>> Sent: Tuesday, October 29, 2013 4:41 PM
>> To: Du, ChangbinX
>> Cc: oli...@neukum.org; linux-usb@vger.kernel.org; net...@vger.kernel.org;
>> linux-ker...@vger.kernel.org
>> Subj
> From: Bjørn Mork [mailto:bj...@mork.no]
> Sent: Tuesday, October 29, 2013 4:41 PM
> To: Du, ChangbinX
> Cc: oli...@neukum.org; linux-usb@vger.kernel.org; net...@vger.kernel.org;
> linux-ker...@vger.kernel.org
> Subject: Re: [PATCH] net/cdc_ncm: fix null pointer panic at
David Miller writes:
> The problem is in cdc_ncm_bind_common().
>
> It seems to leave dangling interface data pointers in some cases, and
> then branches just to "error" so that they don't get cleared back out.
Sorry, but I fail to see this as well. I see one "return" and two "goto
error", but
From: "Du, ChangbinX"
Date: Tue, 29 Oct 2013 03:30:42 +
> In cdc_ncm_bind() function, it call cdc_ncm_bind_common() to setup usb.
> But cdc_ncm_bind_common() may meet error and cause usbnet_disconnect()
> be called which calls free_netdev(net). Thus usbnet structure(alloced
> with net_device
"Du, ChangbinX" writes:
> From: "Du, Changbin"
>
> In cdc_ncm_bind() function, it call cdc_ncm_bind_common() to setup usb.
> But cdc_ncm_bind_common() may meet error and cause usbnet_disconnect()
> be called which calls free_netdev(net).
I am sure you are right, but I really don't see how that
