From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: Alexey Khoroshilov <khoroshilov@ispras.ru>,
devel@driverdev.osuosl.org, ldv-project@linuxtesting.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: ft1000: fix memory leak on error path in ft1000_probe()
Date: Mon, 10 Jun 2013 23:37:03 -0700 [thread overview]
Message-ID: <20130611063703.GB2380@kroah.com> (raw)
In-Reply-To: <CAAfyv348JfJs-FbL3zvQgQ1i=MONVJWdhgfmqzdYOvGxcPAK0Q@mail.gmail.com>
On Mon, Jun 10, 2013 at 10:40:19PM +0200, Belisko Marek wrote:
> Hi Alexey,
>
> On Mon, Jun 10, 2013 at 9:29 PM, Alexey Khoroshilov
> <khoroshilov@ispras.ru> wrote:
> > ft1000dev->tx_urb and ft1000dev->rx_urb are not deallocated
> > if something goes wrong in ft1000_probe(). Also there is no
> > check for success of urb allocation. The patch fixes the both issues.
> >
> > By the way, there is no sense in GFP_ATOMIC for urb allocation here,
> > so it is changed to GFP_KERNEL.
> >
> > Found by Linux Driver Verification project (linuxtesting.org).
> >
> > Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
> > ---
> > drivers/staging/ft1000/ft1000-usb/ft1000_usb.c | 10 ++++++++--
> > 1 file changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/ft1000/ft1000-usb/ft1000_usb.c b/drivers/staging/ft1000/ft1000-usb/ft1000_usb.c
> > index 614db55..29a7cd2 100644
> > --- a/drivers/staging/ft1000/ft1000-usb/ft1000_usb.c
> > +++ b/drivers/staging/ft1000/ft1000-usb/ft1000_usb.c
> > @@ -79,8 +79,12 @@ static int ft1000_probe(struct usb_interface *interface,
> > ft1000dev->dev = dev;
> > ft1000dev->status = 0;
> > ft1000dev->net = NULL;
> > - ft1000dev->tx_urb = usb_alloc_urb(0, GFP_ATOMIC);
> > - ft1000dev->rx_urb = usb_alloc_urb(0, GFP_ATOMIC);
> > + ft1000dev->tx_urb = usb_alloc_urb(0, GFP_KERNEL);
> Can we check return value for tx here? If allocation fails it makes no sense to
> try allocate also rx. Otherwise looks good. Thanks.
> > + ft1000dev->rx_urb = usb_alloc_urb(0, GFP_KERNEL);
> Same for rx here.
> > + if (!ft1000dev->tx_urb || !ft1000dev->rx_urb) {
Both of these allocations are checked here, so it's fine, no need to
change anything.
greg k-h
prev parent reply other threads:[~2013-06-11 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 19:29 Alexey Khoroshilov
2013-06-10 20:40 ` Belisko Marek
2013-06-11 6:37 ` 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=20130611063703.GB2380@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.belisko@gmail.com \
/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
all inboxes | Powered by JetHome®