From: "David S. Miller" <davem@davemloft.net>
To: Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de>
Cc: netdev@oss.sgi.com, greearb@candelatech.com, shemminger@osdl.org
Subject: Re: Bad: scheduling while atomic! in 2.6.8.1
Date: Wed, 8 Sep 2004 21:26:59 -0700 [thread overview]
Message-ID: <20040908212659.4cd99935.davem@davemloft.net> (raw)
In-Reply-To: <200409082342.37273.wolfgang.walter@studentenwerk.mhn.de>
On Wed, 8 Sep 2004 23:42:37 +0200
Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de> wrote:
> We see the exactly the same with 2.6.8.1.
>
> Our host has 3 nics (all 3 are intel e100). We are using vlan, iptables (no
> nat or connection tracking, though) and ipsec. We tested it on other hardware
> (different mainboard, different nics) and the problem remains.
>
> We are getting the log for every received packet, doesn't matter if these are
> dhcp-requests, pings or something else.
You have CONFIG_PREEMPT enabled don't you?
This should fix it, it's a bug in Stephen's conversion of the VLAN
code over to use RCU locking.
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/09/08 21:07:49-07:00 davem@nuts.davemloft.net
# [VLAN]: Fix thinko in RCU locking.
#
# Signed-off-by: David S. Miller <davem@davemloft.net>
#
# net/8021q/vlan_dev.c
# 2004/09/08 21:07:19-07:00 davem@nuts.davemloft.net +1 -1
# [VLAN]: Fix thinko in RCU locking.
#
diff -Nru a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
--- a/net/8021q/vlan_dev.c 2004-09-08 21:08:30 -07:00
+++ b/net/8021q/vlan_dev.c 2004-09-08 21:08:30 -07:00
@@ -244,7 +244,7 @@
/* TODO: Add a more specific counter here. */
stats->rx_errors++;
}
- rcu_read_lock();
+ rcu_read_unlock();
return 0;
}
next prev parent reply other threads:[~2004-09-09 4:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 21:42 Bad: scheduling while atomic! in 2.6.8.1 Wolfgang Walter
2004-09-09 4:26 ` David S. Miller [this message]
2004-09-09 11:56 ` Wolfgang Walter
-- strict thread matches above, loose matches on Subject: below --
2004-09-02 15:40 Andre Correa
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=20040908212659.4cd99935.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
--cc=wolfgang.walter@studentenwerk.mhn.de \
/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).