netdev
[Top] [All Lists]

Re: [Openswan dev] IPComp

To: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Openswan dev] IPComp
From: Paul Wouters <paul@xxxxxxxxxxxxx>
Date: Sat, 3 Jul 2004 13:02:56 +0200 (MET DST)
Cc: Paul Wouters <paul@xxxxxxxxxxxxx>, "D. Hugh Redelmeier" <hugh@xxxxxxxxxx>, <dev@xxxxxxxxxxxxxxxxxx>, Dominique Blas <ml@xxxxxxxx>, <jmorris@xxxxxxxxxx>, <netdev@xxxxxxxxxxx>
In-reply-to: <E1BgYk6-0007M3-00@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Sat, 3 Jul 2004, Herbert Xu wrote:

> > He mailed me the barfs seperately. the key line is:
> > 
> > Jul  2 15:57:30 vin pluto[29579]: "BRU" #3: ERROR: netlink response for Add 
> > SA comp.661a@xxxxxxxxxxxxxxx included errno 12: Cannot allocate memory
> > Jul  2 15:57:30 vin pluto[29579]: "BRU" #4: ERROR: netlink response for Add 
> > SA comp.661a@xxxxxxxxxxxxxxx included errno 12: Cannot allocate memory
> 
> These indicate that a kmalloc in the path of adding IPCOMP SAs failed.
> 
> Hmm, there is a 64K kmalloc in ipcomp_init_state.  That's the most likely
> culprit.  What does cat /proc/slabinfo show?

That information is not listed in the barf.
 
> It'd also be nice to know exactly what kernel version he is using.

2.6.5 

He seems to have generic memory problems though, so I don't think this is an 
openswan or kernel ipsec bug.

Paul
-- 

<Reverend> IRC is just multiplayer notepad.



<Prev in Thread] Current Thread [Next in Thread>