Herbert Xu wrote:
> Marco Berizzi <[EMAIL PROTECTED]> wrote:
> >
> > AFAIK it was applied to osw 2.4.2
> > Also changelog confirm this:
> >
> > v2.4.2
>
> Indeed. Somehow I couldn't find the patch in the git tree that
> I had here. It wasn't the 2.4 branch though.
>
> I presume you're using 2.4.
Marco Berizzi <[EMAIL PROTECTED]> wrote:
>
> AFAIK it was applied to osw 2.4.2
> Also changelog confirm this:
>
> v2.4.2
Indeed. Somehow I couldn't find the patch in the git tree that
I had here. It wasn't the 2.4 branch though.
I presume you're using 2.4.x as well?
If so I'll neet to look a
Herbert Xu wrote:
> Marco Berizzi <[EMAIL PROTECTED]> wrote:
> > I'm experimenting the problem described in this
> > bug report http://bugs.xelerance.com/view.php?id=726
>
> It's actually a bug in openswan. I even sent them a patch for
> it back in June 2005:
>
> http://bugs.xelerance.com/view.ph
Marco Berizzi <[EMAIL PROTECTED]> wrote:
> I'm experimenting the problem described in this
> bug report http://bugs.xelerance.com/view.php?id=726
It's actually a bug in openswan. I even sent them a patch for
it back in June 2005:
http://bugs.xelerance.com/view.php?id=344
Unfortunately it probab
Hello everybody.
I'm experimenting the problem described in this
bug report http://bugs.xelerance.com/view.php?id=726
The system is running vanilla 2.6.19.2 on Slackware
10.1 (gcc 3.3.5, glibc 2.3.5)
I'm available for any kind of test.
TIA
PS: I see a lot kernel memory allocation:
[EMAIL PROTECT
