From: Ian Campbell <icampbell@arcom.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Nicolas Pitre <nico@cam.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: "deadlock" between smc91x driver and link_watch
Date: Wed, 24 Nov 2004 09:58:16 +0000 [thread overview]
Message-ID: <1101290297.10841.15.camel@icampbell-debian> (raw)
In-Reply-To: <20041124014650.47af8ae4.akpm@osdl.org>
On Wed, 2004-11-24 at 01:46 -0800, Andrew Morton wrote:
> Ian Campbell <icampbell@arcom.com> wrote:
> >
> > On Tue, 2004-11-23 at 15:31 -0800, Andrew Morton wrote:
> > > One possible fix would be to remove that flush_scheduled_work() and to do
> > > refcounting around smc_phy_configure(): dev_hold() when scheduling the work
> > > (if schedule_work() returned true), dev_put() in the handler.
> >
> > Something like the following?
>
> I think so.
>
> > +static void smc_phy_configure_wq(void *data)
> > +{
> > + struct net_device *dev = data;
> > + dev_put(dev);
> > + smc_phy_configure(data);
> > +}
>
> You'd want to do the dev_put() after the smc_phy_configure() though. It
> may still be a tiny bit racy against module unload.
Quite right. Fixed patch included.
Signed-off-by: Ian Campbell <icampbell@arcom.com>
Index: 2.6/drivers/net/smc91x.c
===================================================================
--- 2.6.orig/drivers/net/smc91x.c 2004-11-16 09:26:52.000000000 +0000
+++ 2.6/drivers/net/smc91x.c 2004-11-24 09:53:54.397248397 +0000
@@ -1158,6 +1158,20 @@
}
/*
+ * smc_phy_configure_wq
+ *
+ * The net_device is referenced when the work was scheduled to avoid
+ * the need for a flush_scheduled_work() in smc_close(). Drop the
+ * reference and then do the configuration.
+ */
+static void smc_phy_configure_wq(void *data)
+{
+ struct net_device *dev = data;
+ smc_phy_configure(data);
+ dev_put(dev);
+}
+
+/*
* smc_phy_interrupt
*
* Purpose: Handle interrupts relating to PHY register 18. This is
@@ -1350,10 +1364,13 @@
/*
* Reconfiguring the PHY doesn't seem like a bad idea here, but
* smc_phy_configure() calls msleep() which calls schedule_timeout()
- * which calls schedule(). Ence we use a work queue.
+ * which calls schedule(). Hence we use a work queue.
*/
- if (lp->phy_type != 0)
- schedule_work(&lp->phy_configure);
+ if (lp->phy_type != 0) {
+ if (schedule_work(&lp->phy_configure)) {
+ dev_hold(dev);
+ }
+ }
/* We can accept TX packets again */
dev->trans_start = jiffies;
@@ -1536,10 +1553,8 @@
/* clear everything */
smc_shutdown(dev);
- if (lp->phy_type != 0) {
- flush_scheduled_work();
+ if (lp->phy_type != 0)
smc_phy_powerdown(dev, lp->mii.phy_id);
- }
if (lp->pending_tx_skb) {
dev_kfree_skb(lp->pending_tx_skb);
@@ -1891,7 +1906,7 @@
dev->ethtool_ops = &smc_ethtool_ops;
tasklet_init(&lp->tx_task, smc_hardware_send_pkt, (unsigned long)dev);
- INIT_WORK(&lp->phy_configure, smc_phy_configure, dev);
+ INIT_WORK(&lp->phy_configure, smc_phy_configure_wq, dev);
lp->mii.phy_id_mask = 0x1f;
lp->mii.reg_num_mask = 0x1f;
lp->mii.force_media = 0;
--
Ian Campbell, Senior Design Engineer
Web: http://www.arcom.com
Arcom, Clifton Road, Direct: +44 (0)1223 403 465
Cambridge CB1 7EA, United Kingdom Phone: +44 (0)1223 411 200
next prev parent reply other threads:[~2004-11-24 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1101230194.14370.12.camel@icampbell-debian>
2004-11-23 23:31 ` "deadlock" between smc91x driver and link_watch Andrew Morton
2004-11-24 9:41 ` Ian Campbell
2004-11-24 9:46 ` Andrew Morton
2004-11-24 9:58 ` Ian Campbell [this message]
2004-11-24 15:21 ` Nicolas Pitre
2004-11-24 15:52 ` Ian Campbell
2004-11-24 16:57 ` Nicolas Pitre
2004-11-24 17:13 ` Ian Campbell
2004-11-25 9:59 ` Ian Campbell
2004-11-25 16:31 ` Nicolas Pitre
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=1101290297.10841.15.camel@icampbell-debian \
--to=icampbell@arcom.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=nico@cam.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).