From: Olaf Kirch <okir@suse.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] Deadlock in af_packet/packet_rcv
Date: Tue, 30 Nov 2004 11:48:04 +0100 [thread overview]
Message-ID: <20041130104804.GC16970@suse.de> (raw)
In-Reply-To: <20041129200220.25ff3f7a.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
On Mon, Nov 29, 2004 at 08:02:20PM -0800, David S. Miller wrote:
> If it's only the dev_queue_xmit_nit() handlers which all want
> BHs disabled, why don't we just disable BHs in that function?
That was my original fix (see attachment), but Andi Kleen suggested to
actually disable BHs at that level; I think as a matter of caution.
Olaf
--
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?"
[-- Attachment #2: netdev-xmit --]
[-- Type: text/plain, Size: 626 bytes --]
Index: linux-2.6.9/net/core/dev.c
===================================================================
--- linux-2.6.9.orig/net/core/dev.c 2004-10-18 23:54:08.000000000 +0200
+++ linux-2.6.9/net/core/dev.c 2004-11-30 11:46:39.000000000 +0100
@@ -1094,9 +1094,15 @@ void dev_queue_xmit_nit(struct sk_buff *
skb2->nh.raw = skb2->data;
}
+ /* The packet handler may expect BHs to be disabled,
+ * so don't let them down */
+ local_bh_disable();
+
skb2->h.raw = skb2->nh.raw;
skb2->pkt_type = PACKET_OUTGOING;
ptype->func(skb2, skb->dev, ptype);
+
+ local_bh_enable();
}
}
rcu_read_unlock();
next prev parent reply other threads:[~2004-11-30 10:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 20:55 [PATCH] Deadlock in af_packet/packet_rcv Olaf Kirch
2004-11-30 4:02 ` David S. Miller
2004-11-30 10:48 ` Olaf Kirch [this message]
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=20041130104804.GC16970@suse.de \
--to=okir@suse.de \
--cc=davem@davemloft.net \
--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).