Linux USB
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: linux-usb@vger.kernel.org,
	Himadri Pandya <himadrispandya@gmail.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] USB: serial: kl5kusb105: fix memleak on open
Date: Fri, 4 Dec 2020 13:16:26 +0100	[thread overview]
Message-ID: <X8oomifWO//FvDMT@kroah.com> (raw)
In-Reply-To: <X8oYPir8HfGEoTzB@localhost>

On Fri, Dec 04, 2020 at 12:06:38PM +0100, Johan Hovold wrote:
> On Fri, Dec 04, 2020 at 09:55:19AM +0100, Johan Hovold wrote:
> > Fix memory leak of control-message transfer buffer on successful open().
> > 
> > Fixes: 6774d5f53271 ("USB: serial: kl5kusb105: fix open error path")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Johan Hovold <johan@kernel.org>
> > ---
> > 
> > While reviewing Himadri's control-message series I noticed we have a
> > related bug in klsi_105_open() that needs fixing.
> > 
> > 
> >  drivers/usb/serial/kl5kusb105.c | 10 ++++------
> >  1 file changed, 4 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/usb/serial/kl5kusb105.c b/drivers/usb/serial/kl5kusb105.c
> > index 5ee48b0650c4..5f6b82ebccc5 100644
> > --- a/drivers/usb/serial/kl5kusb105.c
> > +++ b/drivers/usb/serial/kl5kusb105.c
> > @@ -276,12 +276,12 @@ static int  klsi_105_open(struct tty_struct *tty, struct usb_serial_port *port)
> >  	priv->cfg.unknown2 = cfg->unknown2;
> >  	spin_unlock_irqrestore(&priv->lock, flags);
> >  
> > +	kfree(cfg);
> > +
> >  	/* READ_ON and urb submission */
> >  	rc = usb_serial_generic_open(tty, port);
> > -	if (rc) {
> > -		retval = rc;
> > -		goto err_free_cfg;
> > -	}
> > +	if (rc)
> > +		return rc;
> >  
> >  	rc = usb_control_msg(port->serial->dev,
> >  			     usb_sndctrlpipe(port->serial->dev, 0),
> > @@ -324,8 +324,6 @@ static int  klsi_105_open(struct tty_struct *tty, struct usb_serial_port *port)
> >  			     KLSI_TIMEOUT);
> >  err_generic_close:
> >  	usb_serial_generic_close(port);
> > -err_free_cfg:
> > -	kfree(cfg);
> >  
> >  	return retval;
> >  }
> 
> I've applied this one now so that I can include it in my pull-request
> for -rc7.
> 
> Greg, just let me know if you think I should hold this one off for 5.11
> instead.

Nope, it's fine to take this now, thanks.

greg k-h

      reply	other threads:[~2020-12-04 12:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  8:55 [PATCH] USB: serial: kl5kusb105: fix memleak on open Johan Hovold
2020-12-04 11:06 ` Johan Hovold
2020-12-04 12:16   ` Greg Kroah-Hartman [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=X8oomifWO//FvDMT@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=himadrispandya@gmail.com \
    --cc=johan@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@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