<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2769" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi again,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I did some more testing. Here's what I've
done:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Compiled kernel-2.6.13-1.1532_FC4 (based on
2.6.13.4) with NAT-T and KLIPS static. Everything works, no errors
reported.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Compiled both kernel-2.6.14-1.1637_FC4 (based
on 2.6.14.1) and kernel-2.6.14-1.1644_FC4 (based on 2.6.14.3) with NAT-T and
KLIPS static. Every time I first start klips on the system, with any of these
kernels I get:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Dec 13 11:51:35 inet kernel: BUG: rwlock recursion
on CPU#0, klipsdebug/15668, f8fd6d40 (Not tainted)<BR>Dec 13 11:51:35 inet
kernel: [<c01d222c>] _raw_write_lock+0x56/0x58<BR>Dec 13 11:51:35
inet kernel: [<f8f9379f>] pfkey_sock_list_grab+0xf/0xc4
[ipsec]<BR>Dec 13 11:51:35 inet kernel: [<c014a6f7>]
do_no_page+0x16e/0x301<BR>Dec 13 11:51:35 inet kernel: [<f8f93bce>]
pfkey_remove_socket+0x14/0xaf [ipsec]<BR>Dec 13 11:51:35 inet kernel:
[<f8f93c86>] pfkey_destroy_socket+0x1d/0x40d [ipsec]<BR>Dec 13 11:51:35
inet kernel: [<f8f94683>] pfkey_release+0x49/0x107 [ipsec]<BR>Dec 13
11:51:35 inet kernel: [<c02a452d>] sock_fasync+0x9a/0x149<BR>Dec 13
11:51:35 inet kernel: [<c02a3a4d>] sock_release+0x14/0x72<BR>Dec 13
11:51:35 inet kernel: [<c02a4479>] sock_close+0x1e/0x38<BR>Dec 13
11:51:35 inet kernel: [<c0159675>] __fput+0xb1/0x178<BR>Dec 13
11:51:35 inet kernel: [<c0157f82>] filp_close+0x3e/0x62<BR>Dec 13
11:51:35 inet kernel: [<c0102eb1>]
syscall_call+0x7/0xb<BR></FONT></DIV>
<DIV><FONT face=Arial size=2>I'ts exacltly the same warning message on both
kernels, so I'm guessing there's a "problem" with openswan-2.4.5dr3 and kernels
based on kernel-2.6.14, since kernel-2.6.13-1.1532_FC4 reports no errors. The
curious thing is: pluto doesn't crash, and the tunnel is still brought up.
If I restart openswan, I don't get the error again. It only hapens with the
first ipsec start after the reboot. I can't reproduce it, unless I reboot the
system. I guess that's not a critcal error. I still need to test the stability
of the tunnel, but as far as I can see, it works normally, even with the
warnings.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>To exclude the KLIPS code, I've also builded
kernel-2.6.14-1.1637_FC4 and kernel-2.6.14-1.1644_FC4 with only NAT-T patch
and compiled KLIPS as a module. Same thing hapens, so it's not the
patch.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I know openswan-2.4.5dr3 is still in development,
so I'm only posting those to share my experiences with it. I also would like to
know: is it something to worry about or I can safely ignore those
messages?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Giovani</FONT></DIV></BODY></HTML>