All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Bill Crowell <bill@crowellsystems.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	James Morris <jmorris@redhat.com>,
	akpm@osdl.org, netdev@oss.sgi.com, mg@iceni.pl
Subject: Re: Fw: ipsec hang
Date: Tue, 30 Nov 2004 00:54:39 +0100	[thread overview]
Message-ID: <41ABB6BF.4080205@trash.net> (raw)
In-Reply-To: <41ABA014.4090309@crowellsystems.com>

[-- Attachment #1: Type: text/plain, Size: 316 bytes --]

Bill Crowell wrote:

> Re the bk12, is there just 1 patch that I should install to 2.6.10-rc2 
> to test IPSec? If I don't fiddle with the mm code, we might be able to 
> make some progress on this part. I just love simultaneous equations 
> with 1000 or more variables... ;-)

Patch is attached.

Regards
Patrick



[-- Attachment #2: x --]
[-- Type: text/plain, Size: 1239 bytes --]

# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
#   2004/11/23 18:21:09-08:00 kaber@trash.net 
#   [XFRM]: Fix endless loop in xfrm_policy_insert
#   
#   The patch 'Fix policy update bug when increasing
#   priority of last policy' broke this, when a policy
#   with lower priority than an existing policy is inserted
#   xfrm_policy_insert loops forever.
#   
#   Signed-off-by: Patrick McHardy <kaber@trash.net>
#   Signed-off-by: David S. Miller <davem@davemloft.net>
# 
# net/xfrm/xfrm_policy.c
#   2004/11/23 18:20:49-08:00 kaber@trash.net +1 -0
#   [XFRM]: Fix endless loop in xfrm_policy_insert
#   
#   The patch 'Fix policy update bug when increasing
#   priority of last policy' broke this, when a policy
#   with lower priority than an existing policy is inserted
#   xfrm_policy_insert loops forever.
#   
#   Signed-off-by: Patrick McHardy <kaber@trash.net>
#   Signed-off-by: David S. Miller <davem@davemloft.net>
# 
diff -Nru a/net/xfrm/xfrm_policy.c b/net/xfrm/xfrm_policy.c
--- a/net/xfrm/xfrm_policy.c	2004-11-30 00:51:18 +01:00
+++ b/net/xfrm/xfrm_policy.c	2004-11-30 00:51:18 +01:00
@@ -353,6 +353,7 @@
 			newpos = p;
 		if (delpol)
 			break;
+		p = &pol->next;
 	}
 	if (newpos)
 		p = newpos;

      reply	other threads:[~2004-11-29 23:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24  1:31 Fw: ipsec hang Andrew Morton
2004-11-24 18:10 ` Patrick McHardy
2004-11-24 22:30   ` James Morris
2004-11-25 10:22     ` Herbert Xu
2004-11-25 12:36       ` Patrick McHardy
2004-11-29 14:16         ` Bill Crowell
2004-11-29 22:17         ` Bill Crowell
2004-11-29 23:54           ` Patrick McHardy [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=41ABB6BF.4080205@trash.net \
    --to=kaber@trash.net \
    --cc=akpm@osdl.org \
    --cc=bill@crowellsystems.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jmorris@redhat.com \
    --cc=mg@iceni.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.