mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: gregkh@linuxfoundation.org, robsonde@gmail.com,
	tvboxspy@gmail.com, mayhs11saini@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192e: set priv->irq as 0 after the irq is freed
Date: Tue, 31 Oct 2017 13:59:57 +0300	[thread overview]
Message-ID: <20171030105532.jm5i2royvm32iqqk@mwanda> (raw)
In-Reply-To: <57b20b92720091f1cdb63f08714ef94a41aee885.1509171955.git.arvind.yadav.cs@gmail.com>

On Sat, Oct 28, 2017 at 12:03:46PM +0530, Arvind Yadav wrote:
> _rtl92e_init can fail here, we must set priv->irq as 0 after free_irq.
> 

The changelog isn't useful.  It should say that we are doing this
because we call free_irq() again in _rtl92e_pci_probe() so it's a double
free.

This fix won't work.  _rtl92e_pci_probe() doesn't check if priv->irq is
zero, and also it frees dev->irq which is different from priv->irq.  We
should really just get rid of priv->irq.

Really each allocation function should have a corresponding free
function so there should be a _rtl92e_undo_init() which frees the memory
and the IRQ.  Currently we just free the IRQ and leak the memory.

Anyway, the right fix is to just do this:

--- a/drivers/staging/rtl8192e/rtl8192e/rtl_core.c
+++ b/drivers/staging/rtl8192e/rtl8192e/rtl_core.c
@@ -2524,7 +2524,7 @@ static int _rtl92e_pci_probe(struct pci_dev *pdev,
        RT_TRACE(COMP_INIT, "Driver probe completed1\n");
        if (_rtl92e_init(dev) != 0) {
                netdev_warn(dev, "Initialization failed");
-               goto err_free_irq;
+               goto err_unmap;
        }
 
        netif_carrier_off(dev);

_rtl92e_init() is a useless name as well...  :/  It would be nice to
preserve the error codes, except they are all -1 which is lazy and
wrong.

regards,
dan carpenter

      reply	other threads:[~2017-10-31 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28  6:33 Arvind Yadav
2017-10-31 10:59 ` Dan Carpenter [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=20171030105532.jm5i2royvm32iqqk@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mayhs11saini@gmail.com \
    --cc=robsonde@gmail.com \
    --cc=tvboxspy@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®