From: "David S. Miller" <davem@davemloft.net>
To: Harald Welte <laforge@netfilter.org>
Cc: netdev@oss.sgi.com, netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.6] 2/2: Fix NAT helper locking
Date: Fri, 3 Sep 2004 00:24:53 -0700 [thread overview]
Message-ID: <20040903002453.77beee16.davem@davemloft.net> (raw)
In-Reply-To: <20040903070234.GQ26263@sunbeam.de.gnumonks.org>
On Fri, 3 Sep 2004 09:02:34 +0200
Harald Welte <laforge@netfilter.org> wrote:
> This is the second of a two part patch.
>
> This part fixes the locking in NAT helpers.
>
> Please apply, Thanks.
Applied both patches, but the first had serious offsets
and the second had to be applied by hand due to rejects
against the current 2.6.x sources.
Ummm... wow what ancient tree did you patch against
Harald? The tree you patched against didn't even have the
skb_header_pointer() changes in it, that's caveman
era :-) That's what caused the rejects.
Anyways, I merged it all in cleanly.
Thanks.
next prev parent reply other threads:[~2004-09-03 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 7:02 [PATCH 2.6] 2/2: Fix NAT helper locking Harald Welte
2004-09-03 7:24 ` David S. Miller [this message]
2004-09-03 15:53 ` Patrick McHardy
2004-09-04 20:05 ` Harald Welte
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=20040903002453.77beee16.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;
as well as URLs for NNTP newsgroup(s).