From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: RFC: Reproducible oops with lockdep on count_matching_names()
Date: Thu, 1 Nov 2007 15:49:09 -0400 [thread overview]
Message-ID: <20071101194909.GF14943@tuxdriver.com> (raw)
In-Reply-To: <20071101191716.GA3201@pogo>
On Thu, Nov 01, 2007 at 03:17:16PM -0400, Luis R. Rodriguez wrote:
> So I started reviewing the probes on each driver and came up with this
> patch because Documenation/pci.txt has:
>
> "The device driver needs to call pci_request_region() to verify
> no other device is already using the same address resource.
> Conversely, drivers should call pci_release_region() AFTER
> calling pci_disable_device(). The idea is to prevent two devices
> colliding on the same address range"
No idea off the top of my head if this relates to the problem or not...
> --- a/drivers/net/wireless/ath5k/base.c
> +++ b/drivers/net/wireless/ath5k/base.c
> @@ -602,10 +602,10 @@ err_free:
> ieee80211_free_hw(hw);
> err_map:
> pci_iounmap(pdev, mem);
> -err_reg:
> - pci_release_region(pdev, 0);
> err_dis:
> pci_disable_device(pdev);
> +err_reg:
> + pci_release_region(pdev, 0);
> err:
> return ret;
> }
If you do this, don't you need to change any "goto err_reg" to "goto
err_dis" as well?
> --- a/drivers/net/wireless/ipw2200.c
> +++ b/drivers/net/wireless/ipw2200.c
> @@ -11756,10 +11756,10 @@ static int ipw_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
> priv->workqueue = NULL;
> out_iounmap:
> iounmap(priv->hw_base);
> - out_pci_release_regions:
> - pci_release_regions(pdev);
> out_pci_disable_device:
> pci_disable_device(pdev);
> + out_pci_release_regions:
> + pci_release_regions(pdev);
> pci_set_drvdata(pdev, NULL);
> out_free_ieee80211:
> free_ieee80211(priv->net_dev);
Same as last comment, but for out_pci_release_regions and
out_pci_disable_device.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-11-01 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 19:17 RFC: Reproducible oops with lockdep on count_matching_names() Luis R. Rodriguez
2007-11-01 19:49 ` John W. Linville [this message]
2007-11-01 21:29 ` Luis R. Rodriguez
2007-11-01 23:26 ` Michael Wu
2007-11-02 10:58 ` Peter Zijlstra
2007-11-03 19:58 ` Luis R. Rodriguez
2007-11-03 20:06 ` Michael Buesch
2007-11-05 12:00 ` Peter Zijlstra
2007-11-05 12:23 ` Pekka Enberg
2007-11-05 13:03 ` Michael Buesch
2007-11-05 13:56 ` Pekka Enberg
2007-11-05 14:26 ` Michael Buesch
2007-11-05 18:47 ` Christoph Lameter
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=20071101194909.GF14943@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).