RE: [PATCH] usb: gadget: acm: set notify_req to NULL after freed to avoid double free

> On 12/26/2015 04:57 AM, changbin...@intel.com wrote: > > From: "Du, Changbin" > > > > If acm_bind fails before allocate notification and acm->notify_req is > > not set to NULL after freed last time, double free will happen. > > Looks good to me. > > Similar problem can occur with another USB

Re: [PATCH] usb: gadget: acm: set notify_req to NULL after freed to avoid double free

On 12/26/2015 04:57 AM, changbin...@intel.com wrote: > From: "Du, Changbin" > > If acm_bind fails before allocate notification and acm->notify_req is > not set to NULL after freed last time, double free will happen. Looks good to me. Similar problem can occur with another USB functions (at

RE: [PATCH] usb: gadget: acm: set notify_req to NULL after freed to avoid double free

> On 12/26/2015 04:57 AM, changbin...@intel.com wrote: > > From: "Du, Changbin" > > > > If acm_bind fails before allocate notification and acm->notify_req is > > not set to NULL after freed last time, double free will happen. > > Looks good to me. > > Similar problem can

Re: [PATCH] usb: gadget: acm: set notify_req to NULL after freed to avoid double free

On 12/26/2015 04:57 AM, changbin...@intel.com wrote: > From: "Du, Changbin" > > If acm_bind fails before allocate notification and acm->notify_req is > not set to NULL after freed last time, double free will happen. Looks good to me. Similar problem can occur with