From: "David S. Miller" <davem@davemloft.net>
To: laforge@netfilter.org
Cc: netdev@oss.sgi.com, netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.6] fix deadlock with ip_queue and tcp local input path
Date: Mon, 30 May 2005 15:26:13 -0700 (PDT) [thread overview]
Message-ID: <20050530.152613.78709308.davem@davemloft.net> (raw)
In-Reply-To: <20050530180654.GX22760@sunbeam.de.gnumonks.org>
From: Harald Welte <laforge@netfilter.org>
Date: Mon, 30 May 2005 20:06:54 +0200
> I've now tested the suggested solution by Patrick McHardy and Herbert Xu to
> simply use local_bh_{en,dis}able().
>
> Please apply the following patch to mainline.
Will do.
> btw: How do we get this into 2.6.11.x ?
You submit your patch to stable@kernel.org.
But I will take care of this for you Harald, don't
worry about it.
prev parent reply other threads:[~2005-05-30 22:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 14:24 [PATCH 2.6] fix deadlock with ip_queue and tcp local input path Harald Welte
2005-05-26 20:52 ` David S. Miller
2005-05-26 20:58 ` Harald Welte
2005-05-26 21:01 ` David S. Miller
2005-05-26 21:38 ` Herbert Xu
2005-05-27 7:37 ` Harald Welte
2005-05-30 18:06 ` Harald Welte
2005-05-30 22:26 ` David S. Miller [this message]
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=20050530.152613.78709308.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=laforge@netfilter.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.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