From: Patrick McHardy <kaber@trash.net>
To: "Marcin Gibu³a" <mg@iceni.pl>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
"David S. Miller" <davem@davemloft.net>
Subject: Re: ipsec hang
Date: Wed, 24 Nov 2004 02:32:36 +0100 [thread overview]
Message-ID: <41A3E4B4.8080401@trash.net> (raw)
In-Reply-To: <200411240134.50314@senat>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Marcin Gibu³a wrote:
>Hi,
>today I tried to configure ipsec on my linux workstation (with openswan) and
>it hanged just after the init had run /etc/rc.d/init.d/ipsec start.
>It was on linux-2.6.10-rc1-bk20, so I upgraded to 2.6.10-rc2-mm3 but it didn't
>make any difference.
>
>The alt-sysrq-p shows the following call trace:
>xfrm_policy_insert
>xfrm_netlink_rcv
>netlink_data_ready
>netlink_sendmsg
>sock_aio_write
>do_sync_write
>sock_map_fd
>sys_select
>vfs_write
>system_call
>
>The full trace (with regs, etc) is available at
>http://www.iceni.pl/marcin/lockup.jpg
>
>.config attached. This hang is 100%-reproductible for me. I can attach
>openswan config if needed.
>
This patch should fix it. 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.
Regards
Patrick
[-- Attachment #2: x --]
[-- Type: text/plain, Size: 709 bytes --]
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/11/24 02:25:16+01:00 kaber@coreworks.de
# [XFRM]: Fix endless loop in xfrm_policy_insert
#
# Signed-off-by: Patrick McHardy <kaber@trash.net>
#
# net/xfrm/xfrm_policy.c
# 2004/11/24 02:25:07+01:00 kaber@coreworks.de +1 -0
# [XFRM]: Fix endless loop in xfrm_policy_insert
#
# Signed-off-by: Patrick McHardy <kaber@trash.net>
#
diff -Nru a/net/xfrm/xfrm_policy.c b/net/xfrm/xfrm_policy.c
--- a/net/xfrm/xfrm_policy.c 2004-11-24 02:31:08 +01:00
+++ b/net/xfrm/xfrm_policy.c 2004-11-24 02:31:08 +01:00
@@ -353,6 +353,7 @@
newpos = p;
if (delpol)
break;
+ p = &pol->next;
}
if (newpos)
p = newpos;
next prev parent reply other threads:[~2004-11-24 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 0:34 ipsec hang Marcin Gibuła
2004-11-24 1:32 ` Patrick McHardy [this message]
2004-11-24 2:46 ` 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=41A3E4B4.8080401@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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.