linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gertjan van Wingerde <gwingerde@gmail.com>
To: Kulikov Vasiliy <segooon@gmail.com>
Cc: kernel-janitors@vger.kernel.org,
	Ivo van Doorn <IvDoorn@gmail.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	Helmut Schaa <helmut.schaa@googlemail.com>,
	Alban Browaeys <prahal@yahoo.com>,
	linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 06/11] rt2x00: do not use PCI resources before pci_enable_device()
Date: Tue, 3 Aug 2010 18:14:11 +0200	[thread overview]
Message-ID: <AANLkTinzvwP74oNaS+mWRnostnGrZZ-iY2SsjMzo=CW4@mail.gmail.com> (raw)
In-Reply-To: <1280850203-5532-1-git-send-email-segooon@gmail.com>

On Tue, Aug 3, 2010 at 5:43 PM, Kulikov Vasiliy <segooon@gmail.com> wrote:
> IRQ and resource[] may not have correct values until
> after PCI hotplug setup occurs at pci_enable_device() time.
>
> The semantic match that finds this problem is as follows:
>
> // <smpl>
> @@
> identifier x;
> identifier request ~= "pci_request.*|pci_resource.*";
> @@
>
> (
> * x->irq
> |
> * x->resource
> |
> * request(x, ...)
> )
>  ...
> *pci_enable_device(x)
> // </smpl>
>
> Signed-off-by: Kulikov Vasiliy <segooon@gmail.com>

Good catch.

Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>

> ---
>  drivers/net/wireless/rt2x00/rt2x00pci.c |   21 ++++++++++-----------
>  1 files changed, 10 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2x00pci.c b/drivers/net/wireless/rt2x00/rt2x00pci.c
> index 19b262e..63c2cc4 100644
> --- a/drivers/net/wireless/rt2x00/rt2x00pci.c
> +++ b/drivers/net/wireless/rt2x00/rt2x00pci.c
> @@ -240,16 +240,16 @@ int rt2x00pci_probe(struct pci_dev *pci_dev, const struct pci_device_id *id)
>        struct rt2x00_dev *rt2x00dev;
>        int retval;
>
> -       retval = pci_request_regions(pci_dev, pci_name(pci_dev));
> +       retval = pci_enable_device(pci_dev);
>        if (retval) {
> -               ERROR_PROBE("PCI request regions failed.\n");
> +               ERROR_PROBE("Enable device failed.\n");
>                return retval;
>        }
>
> -       retval = pci_enable_device(pci_dev);
> +       retval = pci_request_regions(pci_dev, pci_name(pci_dev));
>        if (retval) {
> -               ERROR_PROBE("Enable device failed.\n");
> -               goto exit_release_regions;
> +               ERROR_PROBE("PCI request regions failed.\n");
> +               goto exit_disable_device;
>        }
>
>        pci_set_master(pci_dev);
> @@ -260,14 +260,14 @@ int rt2x00pci_probe(struct pci_dev *pci_dev, const struct pci_device_id *id)
>        if (dma_set_mask(&pci_dev->dev, DMA_BIT_MASK(32))) {
>                ERROR_PROBE("PCI DMA not supported.\n");
>                retval = -EIO;
> -               goto exit_disable_device;
> +               goto exit_release_regions;
>        }
>
>        hw = ieee80211_alloc_hw(sizeof(struct rt2x00_dev), ops->hw);
>        if (!hw) {
>                ERROR_PROBE("Failed to allocate hardware.\n");
>                retval = -ENOMEM;
> -               goto exit_disable_device;
> +               goto exit_release_regions;
>        }
>
>        pci_set_drvdata(pci_dev, hw);
> @@ -300,13 +300,12 @@ exit_free_reg:
>  exit_free_device:
>        ieee80211_free_hw(hw);
>
> -exit_disable_device:
> -       if (retval != -EBUSY)
> -               pci_disable_device(pci_dev);
> -
>  exit_release_regions:
>        pci_release_regions(pci_dev);
>
> +exit_disable_device:
> +       pci_disable_device(pci_dev);
> +
>        pci_set_drvdata(pci_dev, NULL);
>
>        return retval;
> --
> 1.7.0.4
>
>

  reply	other threads:[~2010-08-03 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 15:43 [PATCH 06/11] rt2x00: do not use PCI resources before pci_enable_device() Kulikov Vasiliy
2010-08-03 16:14 ` Gertjan van Wingerde [this message]
2010-08-04  6:59   ` Ivo Van Doorn

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='AANLkTinzvwP74oNaS+mWRnostnGrZZ-iY2SsjMzo=CW4@mail.gmail.com' \
    --to=gwingerde@gmail.com \
    --cc=IvDoorn@gmail.com \
    --cc=helmut.schaa@googlemail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=prahal@yahoo.com \
    --cc=segooon@gmail.com \
    --cc=users@rt2x00.serialmonkey.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;
as well as URLs for NNTP newsgroup(s).