Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-26 Thread Charles-Edouard Ruault
Joy Latten wrote: i upgraded to vanilla kernel 2.6.20 and while i was using strongswan 2.8.2 to setup an IPSEC VPN i got the following kernel Ooops. I had successfully established the same tunnel a few times, but key renegotiation caused a problem ( both ends did not renegotiate at the same

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-26 Thread Charles-Edouard Ruault
Joy Latten wrote: i upgraded to vanilla kernel 2.6.20 and while i was using strongswan 2.8.2 to setup an IPSEC VPN i got the following kernel Ooops. I had successfully established the same tunnel a few times, but key renegotiation caused a problem ( both ends did not renegotiate at the same

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-15 Thread Charles-Edouard Ruault
Joy Latten wrote: i upgraded to vanilla kernel 2.6.20 and while i was using strongswan 2.8.2 to setup an IPSEC VPN i got the following kernel Ooops. I had successfully established the same tunnel a few times, but key renegotiation caused a problem ( both ends did not renegotiate at the same

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-15 Thread Charles-Edouard Ruault
Joy Latten wrote: i upgraded to vanilla kernel 2.6.20 and while i was using strongswan 2.8.2 to setup an IPSEC VPN i got the following kernel Ooops. I had successfully established the same tunnel a few times, but key renegotiation caused a problem ( both ends did not renegotiate at the same

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread James Morris
On Mon, 12 Feb 2007, David Miller wrote: > Thus, below is the patch I will use to fix this bug: > > 1) Calling xfrm_audit_log() with a NULL object is a BUG() > 2) Setting "result" based upon NULL'ness of the object makes no >sense, either set it to "1" in these cases or use an appropriate >

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread David Miller
From: Joy Latten <[EMAIL PROTECTED]> Date: Mon, 12 Feb 2007 11:44:30 -0600 > This is similar to another bug reported last month. > Here is the patch I sent out then. Please let me know > how it goes. > > Signed-off-by: Joy Latten <[EMAIL PROTECTED]> This whole interface is a complete mess.

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread Charles-Edouard Ruault
Joy Latten wrote: >> i upgraded to vanilla kernel 2.6.20 and while i was using strongswan >> 2.8.2 to setup an IPSEC VPN i got the following kernel Ooops. >> I had successfully established the same tunnel a few times, but key >> renegotiation caused a problem ( both ends did not renegotiate at

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread David Miller
From: Joy Latten <[EMAIL PROTECTED]> Date: Mon, 12 Feb 2007 11:44:30 -0600 > This is similar to another bug reported last month. > Here is the patch I sent out then. Please let me know > how it goes. > > Regards, > Joy > > Signed-off-by: Joy Latten <[EMAIL PROTECTED]> This one is my bad, I

Re:[BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread Joy Latten
>i upgraded to vanilla kernel 2.6.20 and while i was using strongswan >2.8.2 to setup an IPSEC VPN i got the following kernel Ooops. >I had successfully established the same tunnel a few times, but key >renegotiation caused a problem ( both ends did not renegotiate at the >same time so the

[BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread Charles-Edouard Ruault
Hi All, i upgraded to vanilla kernel 2.6.20 and while i was using strongswan 2.8.2 to setup an IPSEC VPN i got the following kernel Ooops. I had successfully established the same tunnel a few times, but key renegotiation caused a problem ( both ends did not renegotiate at the same time so the

[BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread Charles-Edouard Ruault
Hi All, i upgraded to vanilla kernel 2.6.20 and while i was using strongswan 2.8.2 to setup an IPSEC VPN i got the following kernel Ooops. I had successfully established the same tunnel a few times, but key renegotiation caused a problem ( both ends did not renegotiate at the same time so the

Re:[BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread Joy Latten
i upgraded to vanilla kernel 2.6.20 and while i was using strongswan 2.8.2 to setup an IPSEC VPN i got the following kernel Ooops. I had successfully established the same tunnel a few times, but key renegotiation caused a problem ( both ends did not renegotiate at the same time so the tunnel

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread David Miller
From: Joy Latten [EMAIL PROTECTED] Date: Mon, 12 Feb 2007 11:44:30 -0600 This is similar to another bug reported last month. Here is the patch I sent out then. Please let me know how it goes. Regards, Joy Signed-off-by: Joy Latten [EMAIL PROTECTED] This one is my bad, I should have

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread Charles-Edouard Ruault
Joy Latten wrote: i upgraded to vanilla kernel 2.6.20 and while i was using strongswan 2.8.2 to setup an IPSEC VPN i got the following kernel Ooops. I had successfully established the same tunnel a few times, but key renegotiation caused a problem ( both ends did not renegotiate at the

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread David Miller
From: Joy Latten [EMAIL PROTECTED] Date: Mon, 12 Feb 2007 11:44:30 -0600 This is similar to another bug reported last month. Here is the patch I sent out then. Please let me know how it goes. Signed-off-by: Joy Latten [EMAIL PROTECTED] This whole interface is a complete mess. Calling

Re: [BUG] 2.6.20 Oopses in xfrm_audit_log

2007-02-12 Thread James Morris
On Mon, 12 Feb 2007, David Miller wrote: Thus, below is the patch I will use to fix this bug: 1) Calling xfrm_audit_log() with a NULL object is a BUG() 2) Setting result based upon NULL'ness of the object makes no sense, either set it to 1 in these cases or use an appropriate error