Why does this code ignore the data length returned

[SunHui2980]

onos-lib-go/pkg/sctp/connection/socket.go

Line 149 in 689b0f0

dataCount, oobCount, flags, _, err = syscall.Recvmsg(fd, b, oobBuffer, 0)

why dose this code ignore the dataCount from syscall.Recvmsg here, since the ORAN standard some messages have the indefinite length?

Is it OK that it discards the dataCount and creates a fixed length buffer in onos-e2t at the same time ?

https://github.com/onosproject/onos-e2t/blob/9ef17c884e94786226d4004ca0f7325b9cf11fc1/pkg/protocols/e2ap/conn.go#L20

https://github.com/onosproject/onos-e2t/blob/9ef17c884e94786226d4004ca0f7325b9cf11fc1/pkg/protocols/e2ap/conn.go#L155

[adibrastegarnia]

I am wondering if we increase the buffer size in onos-e2t, are we gonna hit the limit again? I am wondering if we should handle it at SCTP level. @SunHui2980 Increasing buffer size in onos-e2t is fine but perhaps you should think if we can address it in SCTP library.