[Openswan Users] Pluto segfault on openswan-2.6.23

[Giovani Moda]

> That's a kernel bug, so tracing the userland process won't help. As
> a workaround, you can try esp=3des and ike=3des-sha1 to avoid the aes
> code.

That didn't help. But I have updates: a new kernel for CentOS 5.3 was
released, and apparently there's a patch for openswan crashes on it, as
per https://bugzilla.redhat.com/show_bug.cgi?id=484590. The good news is
that I no longer get a crash when connecting to openswan-2.6.23 with
protostack=klips. I didn't manage to get L2TP/IPsec working though. Even
with KLIPS it seems that #1004 is still biting. But there's also a
(more) bad news: I got this nice Oops when restarting openswan,
apparently while removing/inserting ipsec.ko:

Oops: 0000 [#1]
SMP
last sysfs file: /class/net/lo/ifindex
Modules linked in: ipsec(U) ccm serpent blowfish twofish ecb xcbc
crypto_hash cbc md5 sha256 sha512 des aes_generic testmgr_cipher testmgr
aead crypto_blkcipher crypto_algapi aes_i586 netconsole autofs4 hidp
ipt_REDIRECT xt_tcpudp ipt_TOS ipt_MASQUERADE iptable_nat ip_nat_ftp
ip_nat ipt_TCPMSS ipt_LOG ipt_REJECT iptable_mangle iptable_filter
xt_multiport xt_state xt_limit xt_conntrack ip_conntrack_ftp
ip_conntrack nfnetlink ip_tables x_tables rfcomm l2cap bluetooth sunrpc
ipv6 xfrm_nalgo crypto_api cpufreq_ondemand acpi_cpufreq dm_multipath
scsi_dh video hwmon backlight sbs i2c_ec button battery asus_acpi ac
parport_pc lp parport sr_mod cdrom i2c_i801 sg tg3 sky2 i2c_core pcspkr
dm_raid45 dm_message dm_region_hash dm_mem_cache dm_snapshot dm_zero
dm_mirror dm_log dm_mod ata_piix ahci libata sd_mod scsi_mod ext3 jbd
uhci_hcd ohci_hcd ehci_hcd
CPU:    3
EIP:    0060:[<c04ec00f>]    Tainted: G      VLI
EFLAGS: 00010297   (2.6.18-164.el5PAE #1)
EIP is at vsnprintf+0x2aa/0x45d
eax: 4ad4a55c   ebx: ffffffff   ecx: 4ad4a55c   edx: fffffffe
esi: f51bb031   edi: f5b7bf10   ebp: ffffffff   esp: f5b7bebc
ds: 007b   es: 007b   ss: 0068
Process grep (pid: 6254, ti=f5b7b000 task=f5b46aa0 task.ti=f5b7b000)
Stack: 00000bd3 f51bb02d 001bb026 0000000a f51bbc00 ffffffff 00000000
f92e8252
       00000bd3 f51bb02d 00000c00 f5b3f800 f92c25b1 f5b7bf10 f5b7bf10
0000002d
       4ad4a55c f92baef1 f51bb02d 00000bd3 f92e824d 4ad4a55c 00000000
f5b7bf6c
Call Trace:
 [<f92c25b1>] ipsec_snprintf+0x27/0x3a [ipsec]
 [<f92baef1>] ipsec_tncfg_get_info+0xe9/0x1c4 [ipsec]
 [<f92bae08>] ipsec_tncfg_get_info+0x0/0x1c4 [ipsec]
 [<c04a4827>] proc_file_read+0x100/0x224
 [<c04a4727>] proc_file_read+0x0/0x224
 [<c047331c>] vfs_read+0x9f/0x141
 [<c047376a>] sys_read+0x3c/0x63
 [<c0404f17>] syscall_call+0x7/0xb
 =======================
Code: 74 24 10 73 03 c6 06 20 4d 46 85 ed 7f f1 e9 a1 00 00 00 8b 0f b8
38 59 64 c0 8b 54 24 14 81 f9 ff 0f 00 00 0f 46 c8 89 c8 eb 06 <80> 38
00 74 07 40 4a 83 fa ff 75 f4 29 c8 f6 44 24 18 10 89 c3
EIP: [<c04ec00f>] vsnprintf+0x2aa/0x45d SS:ESP 0068:f5b7bebc

Sometimes it happens on boot, sometimes on the second on third restart.
So who should I scream for help on this matter? The kernel guys or you
guys? 

I've been testing with Ubuntu also, and I'm getting crashes on it too,
but I'll report those on another thread. 

Thanks,

Giovani
 

__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4503 (20091013) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com