From: Greg KH <greg@kroah.com>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: alan@redhat.com, linux-kernel@vger.kernel.org, david-b@pacbell.net
Subject: Re: [2.4] Memleak in drivers/usb/hub.c::usb_reset_device
Date: Wed, 19 Mar 2003 15:32:19 -0800 [thread overview]
Message-ID: <20030319233218.GA17620@kroah.com> (raw)
In-Reply-To: <20030314200204.GC22018@linuxhacker.ru>
On Fri, Mar 14, 2003 at 11:02:04PM +0300, Oleg Drokin wrote:
> Hello!
>
> On Fri, Mar 14, 2003 at 11:37:19AM -0800, Greg KH wrote:
> > > There seems to be a memleak in drivers/usb/hub.c::usb_reset_device()
> > > on error exit path. See the patch.
> > > Found with help of smatch + enhanced unfree script.
> > And yes, as David said, there is another kind of error in this area for
> > 2.5. Patches to clean that up would be appreciated.
>
> Ok, I guess something like that should work:
I've applied this to my trees, thanks.
greg k-h
prev parent reply other threads:[~2003-03-19 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 19:41 [2.4] Memleak in drivers/usb/hub.c::usb_reset_device Oleg Drokin
2003-03-12 20:00 ` David Brownell
2003-03-14 19:37 ` Greg KH
2003-03-14 20:02 ` Oleg Drokin
2003-03-19 23:32 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030319233218.GA17620@kroah.com \
--to=greg@kroah.com \
--cc=alan@redhat.com \
--cc=david-b@pacbell.net \
--cc=green@linuxhacker.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox