From: Jeff Garzik <jeff@garzik.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: xiong.huang@atheros.com, jie.yang@atheros.com, netdev@vger.kernel.org
Subject: Re: [PATCH] Don't take the mdio_lock in atl1e_probe
Date: Sat, 13 Sep 2008 15:55:54 -0400 [thread overview]
Message-ID: <48CC1ACA.6070101@garzik.org> (raw)
In-Reply-To: <20080812131314.GZ8618@parisc-linux.org>
Matthew Wilcox wrote:
> Lockdep warns about the mdio_lock taken with interrupts enabled then later
> taken from interrupt context. Initially, I considered changing these
> to spin_lock_irq/spin_unlock_irq, but then I looked at atl1e_phy_init()
> and saw that it calls msleep(). Sleeping while holding a spinlock is
> not allowed either.
>
> In the probe path, we haven't registered the interrupt handler, so
> it can't poke at this card yet. It's before we call register_netdev(),
> so I don't think any other threads can reach this card either. If I'm
> right, we don't need a spinlock at all.
>
> Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
>
> diff --git a/drivers/net/atl1e/atl1e_main.c b/drivers/net/atl1e/atl1e_main.c
> index 82d7be1..ba22a51 100644
> --- a/drivers/net/atl1e/atl1e_main.c
> +++ b/drivers/net/atl1e/atl1e_main.c
> @@ -2389,9 +2389,7 @@ static int __devinit atl1e_probe(struct pci_dev *pdev,
> }
>
> /* Init GPHY as early as possible due to power saving issue */
> - spin_lock(&adapter->mdio_lock);
> atl1e_phy_init(&adapter->hw);
> - spin_unlock(&adapter->mdio_lock);
> /* reset the controller to
> * put the device in a known good starting state */
applied
prev parent reply other threads:[~2008-09-13 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 13:13 [PATCH] Don't take the mdio_lock in atl1e_probe Matthew Wilcox
2008-08-13 1:21 ` Jie Yang
2008-09-13 19:55 ` Jeff Garzik [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=48CC1ACA.6070101@garzik.org \
--to=jeff@garzik.org \
--cc=jie.yang@atheros.com \
--cc=matthew@wil.cx \
--cc=netdev@vger.kernel.org \
--cc=xiong.huang@atheros.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).