Re: oops with ipcomp

2008-02-11 Thread Beschorner Daniel
 Does every packet from A trigger the crash?

In my last test the crash was triggered after 300MB of http output (on
the fifth run of a script downloading the same 60MB of data).
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: oops with ipcomp

2008-02-08 Thread Herbert Xu
On Thu, Feb 07, 2008 at 07:01:32PM +0100, Beschorner Daniel wrote:

  Could you show me the exact policies/SAs of the tunnel involved
  in the crash?
 
 esp/cbc(aes128)/hmac(sha1)

No I meant the exact output of ip x p and ip x s.

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: oops with ipcomp

2008-02-08 Thread Beschorner Daniel
 No I meant the exact output of ip x p and ip x s.

I know, but as I end up every time with a tainted kernel on our
production server I didn't turn ipcomp on, but now I got it.

src Net_B dst A
dir in priority 2088 
tmpl src B dst A
proto comp reqid 16394 mode tunnel
level use 
tmpl src 0.0.0.0 dst 0.0.0.0
proto esp reqid 16393 mode transport
src Net_B dst Net_A
dir in priority 2344 
tmpl src B dst A
proto comp reqid 16390 mode tunnel
level use 
tmpl src 0.0.0.0 dst 0.0.0.0
proto esp reqid 16389 mode transport
src A dst Net_B 
dir out priority 2088 
tmpl src A dst B
proto comp reqid 16394 mode tunnel
tmpl src 0.0.0.0 dst 0.0.0.0
proto esp reqid 16393 mode transport
src Net_A dst Net_B
dir out priority 2344 
tmpl src A dst B
proto comp reqid 16390 mode tunnel
tmpl src 0.0.0.0 dst 0.0.0.0
proto esp reqid 16389 mode transport
src Net_B dst A
dir fwd priority 2088 
tmpl src B dst A
proto comp reqid 16394 mode tunnel
level use 
tmpl src 0.0.0.0 dst 0.0.0.0
proto esp reqid 16393 mode transport
src Net_B dst Net_A
dir fwd priority 2344 
tmpl src B dst A
proto comp reqid 16390 mode tunnel
level use 
tmpl src 0.0.0.0 dst 0.0.0.0
proto esp reqid 16389 mode transport

src A dst B
proto comp spi 0x427e reqid 16390 mode tunnel
replay-window 0 
comp deflate 0x
sel src 0.0.0.0/0 dst 0.0.0.0/0 
src B dst A
proto comp spi 0xecf0 reqid 16390 mode tunnel
replay-window 0 
comp deflate 0x
sel src 0.0.0.0/0 dst 0.0.0.0/0 
src A dst B
proto esp spi 0x53f15e96 reqid 16389 mode transport
replay-window 32 
auth hmac(sha1) 0x...
enc cbc(aes) 0x...
sel src 0.0.0.0/0 dst 0.0.0.0/0 
src B dst A
proto esp spi 0x7b329066 reqid 16389 mode transport
replay-window 32 
auth hmac(sha1) 0...
enc cbc(aes) 0x...
sel src 0.0.0.0/0 dst 0.0.0.0/0 
src A dst B
proto (null) spi 0x53ec987a reqid 0 mode tunnel
replay-window 0 
sel src 0.0.0.0/0 dst 0.0.0.0/0 
src B dst A
proto (null) spi 0xc19ef67c reqid 0 mode tunnel
replay-window 0 
sel src 0.0.0.0/0 dst 0.0.0.0/0 
src A dst B
proto comp spi 0x1314 reqid 16394 mode tunnel
replay-window 0 
comp deflate 0x
sel src 0.0.0.0/0 dst 0.0.0.0/0 
src B dst A
proto comp spi 0x32ff reqid 16394 mode tunnel
replay-window 0 
comp deflate 0x
sel src 0.0.0.0/0 dst 0.0.0.0/0 
src A dst B
proto esp spi 0xec7d12de reqid 16393 mode transport
replay-window 32 
auth hmac(sha1) 0x...
enc cbc(aes) 0x...
sel src 0.0.0.0/0 dst 0.0.0.0/0 
src B dst A
proto esp spi 0x75016d2d reqid 16393 mode transport
replay-window 32 
auth hmac(sha1) 0x...
enc cbc(aes) 0x...
sel src 0.0.0.0/0 dst 0.0.0.0/0 
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: oops with ipcomp

2008-02-08 Thread Herbert Xu
On Fri, Feb 08, 2008 at 11:45:33AM +0100, Beschorner Daniel wrote:
  No I meant the exact output of ip x p and ip x s.
 
 I know, but as I end up every time with a tainted kernel on our
 production server I didn't turn ipcomp on, but now I got it.

Hmm, that's pretty much what I've got (but I'm on 32-bit still).

Does every packet from A trigger the crash?

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: oops with ipcomp

2008-02-07 Thread Beschorner Daniel
 OK, so are you now able to reproduce this crash without waiting
 for hours? That would be really helpful in tracking it down.

Yes, I can reproduce it in minutes now.

 Could you show me the exact policies/SAs of the tunnel involved
 in the crash?

esp/cbc(aes128)/hmac(sha1)


Mit freundlichen Grüßen
i.A. Daniel Beschorner
Entwicklung
   
FACTON GmbH
Prager Str. 2
01069 Dresden

Tel.: +49-351-40223-0
Mobil: +49-151-54446012
Fax: +49-351-40223-15
Mail: [EMAIL PROTECTED]
Web: www.facton.com



Neuer FACTON-Unternehmensauftritt im Internet: www.facton.com 
Alle Schulungstermine 2008 in der Übersicht: www.facton.com/akademie2008 



Vertretungsberechtigte Geschäftsführer: Thoralf Nehls, Martin Nehls 
Sitz der Gesellschaft: Prager Straße 2, 01069 Dresden 
Handelsregister: Amtsgericht Dresden HRB 17304




This email message is intended only for the person(s) to whom it is addressed
and as such is confidential. If you have received this communication in error,
please notify us immediately and delete the original message.
Thank you for your cooperation.
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: oops with ipcomp

2008-02-07 Thread Herbert Xu
On Wed, Feb 06, 2008 at 09:55:03PM +0100, Beschorner Daniel wrote:

 A is the oopsing 2.6.24, B is 2.6.23.
 I didn't change anything in the scenario recently, till 2.6.23 all
 worked fine.

OK, so are you now able to reproduce this crash without waiting
for hours? That would be really helpful in tracking it down.

Could you show me the exact policies/SAs of the tunnel involved
in the crash?

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: oops with ipcomp

2008-02-06 Thread Beschorner Daniel
 Unable to handle kernel paging request at c20fb000 RIP: 
  [8031b8f0] deflate_slow+0x40/0x400

Here is some more information about the scenario in which I can easily
reproduce the oops now:

Net_A - GW_A --- GW_B - Net_B

The Net_A - Net_B ESP/AES/IPComp tunnel works fine, the tunnel between
Net_B and the external IP address of GW_A triggers the oops in GW_A.

Daniel
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: oops with ipcomp

2008-02-06 Thread Herbert Xu
On Wed, Feb 06, 2008 at 03:43:25PM +0100, Beschorner Daniel wrote:
 
 Net_A - GW_A --- GW_B - Net_B
 
 The Net_A - Net_B ESP/AES/IPComp tunnel works fine, the tunnel between
 Net_B and the external IP address of GW_A triggers the oops in GW_A.

That's interesting.  So which one out of A and B is running 2.6.24?

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: oops with ipcomp

2008-02-06 Thread Beschorner Daniel
 Net_A - GW_A --- GW_B - Net_B
 The Net_A - Net_B ESP/AES/IPComp tunnel works fine, the tunnel
between
 Net_B and the external IP address of GW_A triggers the oops in GW_A.

 That's interesting.  So which one out of A and B is running 2.6.24?

A is the oopsing 2.6.24, B is 2.6.23.
I didn't change anything in the scenario recently, till 2.6.23 all
worked fine.

Daniel
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: oops with ipcomp

2008-02-04 Thread Beschorner Daniel
 Unable to handle kernel paging request at c20fb000 RIP: 
  [8031b8f0] deflate_slow+0x40/0x400

 I'm not able to get much information out of this crash dump.  Nor
 can I reproduce this bug on my 32-bit machines and I'm currently
 away from my 64-bit machines.

 How long have you been using IPComp in the past and what was the
 last kernel version which was stable with IPComp?

I've never seen this with kernels  2.6.24 after many years of
ipsec/ipcomp usage.
I got it 18 hours after boot, since the oops it runs stable for further
72 hours.
But I cross the fingers that it was an unique issue, I'll report if it
oopses again.

Daniel
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


oops with ipcomp

2008-02-04 Thread Beschorner Daniel
Nope! Right now it happened again, something must have changed with
2.6.24.

Unable to handle kernel paging request at c20fb000 RIP:
 [8031b8f0] deflate_slow+0x40/0x400
PGD 7f845067 PUD 7f846067 PMD 7f847067 PTE 0
Oops:  [1] SMP
CPU 0
Modules linked in:
Pid: 11055, comm: httpd Not tainted 2.6.24 #2
RIP: 0010:[8031b8f0]  [8031b8f0]
deflate_slow+0x40/0x400
RSP: 0018:810039525938  EFLAGS: 00010206
RAX:  RBX: c20b9000 RCX: 000408d8
RDX: c20ba728 RSI:  RDI: 6aa3
RBP: 08d4 R08: 3c8b R09: 1800
R10: 0010 R11: c20b94bc R12: 007d
R13: 0005 R14:  R15: c2097000
FS:  2b16cc187190() GS:805a8000()
knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: c20fb000 CR3: 7c69a000 CR4: 06e0
DR0:  DR1:  DR2: 
DR3:  DR6: 0ff0 DR7: 0400
Process httpd (pid: 11055, threadinfo 810039524000, task
81007f8e6140)
Stack:  81007c4aae10 81007ead4400 0005
c20b9000
 81006c186000 8031c25d  81007ead4400
 81007ead43c0 81006c1860a8 0109 802ff351
Call Trace:
 [8031c25d] zlib_deflate+0x10d/0x330
 [802ff351] deflate_compress+0x91/0xb0
 [804771b8] ipcomp_output+0x98/0x1e0
 [80489ef6] xfrm_output+0x116/0x1e0
 [80482dc4] xfrm4_output_finish2+0x44/0x1e0
 [80483075] xfrm4_output+0x55/0x60
 [80445989] ip_queue_xmit+0x209/0x450
 [8049b0d0] thread_return+0x3d/0x54d
 [8023b094] lock_timer_base+0x34/0x70
 [80456dcf] tcp_transmit_skb+0x40f/0x7c0
 [80458aae] __tcp_push_pending_frames+0x11e/0x940
 [8044cb8e] tcp_sendmsg+0x81e/0xc40
 [80291e3f] dput+0x1f/0x130
 [80410b01] sock_aio_write+0x111/0x120
 [804109f0] sock_aio_write+0x0/0x120
 [8027f95b] do_sync_readv_writev+0xcb/0x110
 [80246850] autoremove_wake_function+0x0/0x30
 [8027fb99] do_sync_read+0xd9/0x120
 [80287941] permission+0x61/0x100
 [8027f7bd] rw_copy_check_uvector+0x9d/0x130
 [802800a2] do_readv_writev+0xe2/0x210
 [8027e1ba] do_filp_open+0x3a/0x50
 [802806e3] sys_writev+0x53/0x90
 [8020bb3e] system_call+0x7e/0x83


Code: 0f b6 14 0a 31 d0 23 43 74 48 8b 53 60 89 43 68 89 c0 0f b7
RIP  [8031b8f0] deflate_slow+0x40/0x400
 RSP 810039525938
CR2: c20fb000
---[ end trace 0ff90cd2723f4b1e ]---
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


oops with ipcomp

2008-02-01 Thread Beschorner Daniel
One more issue with 2.6.24, some hours after I reactivated ipcomp with
Herb's 2 patches.
The httpd log shows a http request per esp tunnel at oops time.
Don't know whether it is for network or compression guys, so I started
posting here.
Daniel

Unable to handle kernel paging request at c20fb000 RIP: 
 [8031b8f0] deflate_slow+0x40/0x400
PGD 7f845067 PUD 7f846067 PMD 7f847067 PTE 0
Oops:  [1] SMP 
CPU 0 
Modules linked in:
Pid: 9136, comm: httpd Not tainted 2.6.24 #2
RIP: 0010:[8031b8f0]  [8031b8f0]
deflate_slow+0x40/0x400
RSP: 0018:81002ad35938  EFLAGS: 00010206
RAX:  RBX: c20b9000 RCX: 000408d8
RDX: c20ba728 RSI:  RDI: 5f65
RBP: 08d4 R08: 3dae R09: 1800
R10: 0010 R11: c20b94bc R12: 01ad
R13: 0005 R14:  R15: c2097000
FS:  2b00bb68b190() GS:805a8000()
knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: c20fb000 CR3: 2ac82000 CR4: 06e0
DR0:  DR1:  DR2: 
DR3:  DR6: 0ff0 DR7: 0400
Process httpd (pid: 9136, threadinfo 81002ad34000, task
81007d2d4080)
Stack:  810042f3f710 81007dfb0700 0005
c20b9000
 81007de89000 8031c25d  81007dfb0700
 81007dfb06c0 81007de890a8 010a 802ff351
Call Trace:
 [8031c25d] zlib_deflate+0x10d/0x330
 [802ff351] deflate_compress+0x91/0xb0
 [804771b8] ipcomp_output+0x98/0x1e0
 [80489ef6] xfrm_output+0x116/0x1e0
 [80482dc4] xfrm4_output_finish2+0x44/0x1e0
 [80483075] xfrm4_output+0x55/0x60
 [80445989] ip_queue_xmit+0x209/0x450
 [8049b0d0] thread_return+0x3d/0x54d
 [8023b094] lock_timer_base+0x34/0x70
 [80456dcf] tcp_transmit_skb+0x40f/0x7c0
 [80458aae] __tcp_push_pending_frames+0x11e/0x940
 [8044cb8e] tcp_sendmsg+0x81e/0xc40
 [80291e3f] dput+0x1f/0x130
 [80410b01] sock_aio_write+0x111/0x120
 [804109f0] sock_aio_write+0x0/0x120
 [8027f95b] do_sync_readv_writev+0xcb/0x110
 [80246850] autoremove_wake_function+0x0/0x30
 [8027fb99] do_sync_read+0xd9/0x120
 [80287941] permission+0x61/0x100
 [8027f7bd] rw_copy_check_uvector+0x9d/0x130
 [802800a2] do_readv_writev+0xe2/0x210
 [8027e1ba] do_filp_open+0x3a/0x50
 [802806e3] sys_writev+0x53/0x90
 [8020bb3e] system_call+0x7e/0x83


Code: 0f b6 14 0a 31 d0 23 43 74 48 8b 53 60 89 43 68 89 c0 0f b7 
RIP  [8031b8f0] deflate_slow+0x40/0x400
 RSP 81002ad35938
CR2: c20fb000
---[ end trace cfeb10aa23b54939 ]---
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: oops with ipcomp

2008-02-01 Thread Herbert Xu
On Fri, Feb 01, 2008 at 11:09:22AM +0100, Beschorner Daniel wrote:
 One more issue with 2.6.24, some hours after I reactivated ipcomp with
 Herb's 2 patches.
 The httpd log shows a http request per esp tunnel at oops time.
 Don't know whether it is for network or compression guys, so I started
 posting here.
 
 Unable to handle kernel paging request at c20fb000 RIP: 
  [8031b8f0] deflate_slow+0x40/0x400

I'm not able to get much information out of this crash dump.  Nor
can I reproduce this bug on my 32-bit machines and I'm currently
away from my 64-bit machines.

How long have you been using IPComp in the past and what was the
last kernel version which was stable with IPComp?

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html