From: Olaf Kirch <okir@suse.de>
To: netdev@oss.sgi.com
Subject: [PATCH] Deadlock in af_packet/packet_rcv
Date: Thu, 25 Nov 2004 21:55:03 +0100 [thread overview]
Message-ID: <20041125205503.GA18083@suse.de> (raw)
Before introduction of lock-less loopback, all of netdev_xmit_nit was
running with bottom halves disabled, and some code seems to rely on
this. One of them is af_packet's packet_rcv handler, which is called
from the receive path via netdev_xmit_nit. It takes a spin lock,
and if an interrupt occurs and calls netdev_xmit during this time,
the CPU deadlocks.
The patch below disables BHs while in the TX path for loopback and
similar devices.
An alternative, less conservative fix would be to just use spin_lock_bh
in af_packet.c.
Signed-off-by: Olaf Kirch <okir@suse.de>
Index: linux-2.6.9/net/core/dev.c
===================================================================
--- linux-2.6.9.orig/net/core/dev.c
+++ linux-2.6.9/net/core/dev.c
@@ -1222,6 +1222,7 @@ int __skb_linearize(struct sk_buff *skb,
}
#define HARD_TX_LOCK(dev, cpu) { \
+ local_disable_bh(); \
if ((dev->features & NETIF_F_LLTX) == 0) { \
spin_lock(&dev->xmit_lock); \
dev->xmit_lock_owner = cpu; \
@@ -1233,6 +1234,7 @@ int __skb_linearize(struct sk_buff *skb,
dev->xmit_lock_owner = -1; \
spin_unlock(&dev->xmit_lock); \
} \
+ local_enable_bh(); \
}
static inline void qdisc_run(struct net_device *dev)
--
Olaf Kirch | Things that make Monday morning interesting, #2:
okir@suse.de | "We have 8,000 NFS mount points, why do we keep
---------------+ running out of privileged ports?"
next reply other threads:[~2004-11-25 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 20:55 Olaf Kirch [this message]
2004-11-30 4:02 ` [PATCH] Deadlock in af_packet/packet_rcv David S. Miller
2004-11-30 10:48 ` Olaf Kirch
2004-11-30 9:32 ` Tommy Christensen
2004-11-30 11:01 ` Olaf Kirch
2004-11-30 11:31 ` Tommy Christensen
2004-11-30 11:45 ` Olaf Kirch
2004-11-30 11:56 ` Tommy Christensen
2004-11-30 21:07 ` David S. Miller
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=20041125205503.GA18083@suse.de \
--to=okir@suse.de \
--cc=netdev@oss.sgi.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).