Vlad, Will these changes make it into the next Kernel release? If so which one will it be?
Thanks, Oscar -----Original Message----- From: Vlad Yasevich [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 01, 2007 3:19 PM To: Isaula Oscar-QOI000 Cc: netdev@vger.kernel.org Subject: Re: [SCTP] Initialization collision problem Isaula Oscar-QOI000 wrote: > Vlad, > > I finally got test results for the changes you suggested. The original > issue is fixed and I have not detected any side effects. Thanks. -vlad > > Thanks, > Oscar > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Vlad Yasevich > Sent: Wednesday, April 11, 2007 9:45 AM > To: Isaula Oscar-QOI000 > Cc: netdev@vger.kernel.org; [EMAIL PROTECTED] > Subject: Re: [SCTP] Initialization collision problem > > Hi Oscar > > Isaula Oscar-QOI000 wrote: >> I ran into a problem where LKSCTP is reporting a SCTM_COMM_UP >> indication to the User application but is giving back a value of zero >> for the assoc_id. >> >> Attached are the SCTP debugs for the period in question. >> >> A couple of things that I would like to note about my setup. One is >> that I'm running Kernel version 2.6.10 (I know is old but I can't >> move > >> to a newer version due to custom drivers). The second thing is that >> the link between the two SCTP node is a very noisy and some messages >> are getting lost (i.e. the INIT_ACK from the peer in this particular > case). > > Can you give this patch a try and let me know if this fixes your issue? > > Thanks > -vlad > - 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
