Re: [Lksctp-developers] Rissue with patching back sctp_getpaddr and sctp_getladdr from 2.6.19 to 2.6.10

[Son L. <so...@no...>]

Thanks Vald. The patch was done at the kernel level which is like a
black box to us. So I assume that if we use the latest lksctp_too.1.0.6
which has the new sctp.h and new implemenation (at user space level ?)
of sctp_getpaddr and sctp_getladdr in addr.c. I am not sure whats the
linkage between the APIS in the addr.c and the kernel.

I have another big question as well.

Does application needs the implementations (e.g. sctp_gepaddr(), ...)
from the lk_sctptool OR just use the sctp.h header file provided by the
tools and call to the APIs will be invoked from the actual kernel.

Thanks,
Son

-----Original Message-----
From: Vlad Yasevich [mailto:vla...@hp...]=20
Sent: Monday, March 26, 2007 10:58 AM
To: Le, Son (CAR:SI52)
Cc: lks...@li...
Subject: Re: Rissue with patching back sctp_getpaddr and sctp_getladdr
from 2.6.19 to 2.6.10

Son Le wrote:
> We also compile the below directory too. Not sure if the 2 APIs=20
> sctp_getladdr and sctp_getpaddr in the addrs.c mismatche with the one=20
> in the kernel source ? The sctp kernel is maintained by other people=20
> and we don't know what is in it.
>=20
> zcarh0xa.ca.nortel.com-149>ls
> Build.mk  bindx.c     opt_info.c  recvmsg.c
> addrs.c   connectx.c  peeloff.c   sendmsg.c
> zcarh0xa.ca.nortel.com-150>
>=20

The API change you want affects both use and kernel space.  You need to
make sure that the sctp library uses the new kernel interface.

Of course, you can always call the socket options directly, but that is
not a recommended way to do this.

-vlad