public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: nardelli <jnardelli@infosciences.com>
To: linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: [PATCH] Memory leak in visor.c and ftdi_sio.c
Date: Fri, 04 Jun 2004 10:59:57 -0400	[thread overview]
Message-ID: <40C08E6D.8080606@infosciences.com> (raw)

Note that I have not verified any of the below on
hardware associated with drivers/usb/serial/ftdi_sio.c,
only with drivers/usb/serial/visor.c.  If anyone has
hardware for this device, I would appreciate your comments.

A memory leak occurs in both drivers/usb/serial/ftdi_sio.c
and drivers/usb/serial/visor.c when the usb device is
unplugged while data is being written to the device.  This
patch should clear that up.

This was prepared against 2.6.7-rc2.

Signed-off-by: Joe Nardelli <jnardelli@infosciences.com>


diff -uprN -X dontdiff linux-2.6.7-rc2.orig/drivers/usb/serial/ftdi_sio.c linux-2.6.7-rc2/drivers/usb/serial/ftdi_sio.c
--- linux-2.6.7-rc2.orig/drivers/usb/serial/ftdi_sio.c  2004-06-04 10:10:21.112743024 -0400
+++ linux-2.6.7-rc2/drivers/usb/serial/ftdi_sio.c       2004-06-04 09:53:27.000000000 -0400
@@ -1504,6 +1504,7 @@ static int ftdi_write (struct usb_serial
       if (status) {
               err("%s - failed submitting write urb, error %d", __FUNCTION__, status);
               count = status;
+               kfree (buffer);
       }

       /* we are done with this urb, so let the host driver
diff -uprN -X dontdiff linux-2.6.7-rc2.orig/drivers/usb/serial/visor.c linux-2.6.7-rc2/drivers/usb/serial/visor.c
--- linux-2.6.7-rc2.orig/drivers/usb/serial/visor.c     2004-06-04 10:10:21.210728128 -0400
+++ linux-2.6.7-rc2/drivers/usb/serial/visor.c  2004-06-04 10:13:10.214035720 -0400
@@ -515,6 +515,7 @@ static int visor_write (struct usb_seria
               dev_err(&port->dev, "%s - usb_submit_urb(write bulk) failed with status = %d\n",
                       __FUNCTION__, status);
               count = status;
+               kfree (buffer);
       } else {
               bytes_out += count;
       }

-- 
Joe Nardelli
jnardelli@infosciences.com


             reply	other threads:[~2004-06-04 15:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 14:59 nardelli [this message]
2004-06-04 16:34 ` [PATCH] Memory leak in visor.c and ftdi_sio.c Ian Abbott
2004-06-04 17:25   ` nardelli
2004-06-04 18:04   ` Pete Zaitcev
2004-06-04 23:16   ` [linux-usb-devel] " Peter Horton
2004-06-05  0:18   ` Greg KH
2004-06-07  9:58     ` Ian Abbott
2004-06-07 14:19     ` nardelli
2004-06-07 15:43       ` Richard B. Johnson
2004-06-07 15:56         ` nardelli
2004-06-04 18:12 ` Greg KH
2004-06-04 18:47   ` nardelli
2004-06-04 22:02     ` Greg KH

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=40C08E6D.8080606@infosciences.com \
    --to=jnardelli@infosciences.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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