From: Stephen Hemminger <shemminger@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: "Paul Rolland" <rol@witbe.net>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [2.6.5] Bad scheduling while atomic
Date: Fri, 16 Apr 2004 13:16:33 -0700 [thread overview]
Message-ID: <20040416131633.1bfbfa4c@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <200404161551.i3GFpD124970@tag.witbe.net>
Bring up/down network devices with lapbether causes scheduling while
atomic (if preempt enabled).
The calls to rcu_read_lock are unnecessary since lapb_device_event
is called from notifier with the rtnetlink semaphore held, it is
already protected from the labp_devices list changing.
Patch against 2.6.6-rc1
diff -Nru a/drivers/net/wan/lapbether.c b/drivers/net/wan/lapbether.c
--- a/drivers/net/wan/lapbether.c Fri Apr 16 11:00:35 2004
+++ b/drivers/net/wan/lapbether.c Fri Apr 16 11:00:35 2004
@@ -392,6 +392,8 @@
/*
* Handle device status changes.
+ *
+ * Called from notifier with RTNL held.
*/
static int lapbeth_device_event(struct notifier_block *this,
unsigned long event, void *ptr)
@@ -402,7 +404,6 @@
if (!dev_is_ethdev(dev))
return NOTIFY_DONE;
- rcu_read_lock();
switch (event) {
case NETDEV_UP:
/* New ethernet device -> new LAPB interface */
@@ -422,7 +423,6 @@
lapbeth_free_device(lapbeth);
break;
}
- rcu_read_unlock();
return NOTIFY_DONE;
}
next prev parent reply other threads:[~2004-04-16 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 15:51 Paul Rolland
2004-04-16 20:16 ` Stephen Hemminger [this message]
2004-04-16 21:56 ` David S. Miller
2004-04-18 18:50 ` Paul Rolland
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=20040416131633.1bfbfa4c@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rol@witbe.net \
/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®