Bug 438082 - interface change for user space sctp API - "struct sctp_paddrparams"
interface change for user space sctp API - "struct sctp_paddrparams"
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lksctp-tools (Show other bugs)
5.0
All Linux
low Severity low
: rc
: ---
Assigned To: Zdenek Prikryl
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-18 17:50 EDT by William Reich
Modified: 2008-04-29 09:07 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-29 09:07:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description William Reich 2008-03-18 17:50:00 EDT
Description of problem:

interface change for user space sctp API - 
The structure "struct sctp_paddrparams" has changed
between RHAS4 and RHAS5. Therefore, the setsockopt() call
fails with inputs of IPPROTO_SCTP and
SCTP_PEER_ADDR_PARAMS.

Is there anything that can be done besides
recode & recompile  of my application ?

Going from RH3 to RH4 did not require any recoding...

I did not see anything in RH5 release notes on this.
Is any documentation available on this topic 
of SCTP interface changes ?



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Zdenek Prikryl 2008-04-29 09:07:45 EDT
Hello,
RHAS4 has lksctp-tools-1.0.2 and RHAS5 has lksctp-tools-1.0.6. According the
changelog in 1.0.6 (/usr/share/doc/lksctp-tool-1.0.6/Changelog), there are some
bugfixes and changes in API. But there are only notes about that.

So there is no other way how to fix it than rewriting && recompiling your
application. If you want to get more detailed information, you'll maybe find
something at official web pages.

Note You need to log in before you can comment on or make changes to this bug.