search for: sctp_sendmsg

...t attempts to send data on a socket that is no longer able to send. In addition, the send operation fails with the error [EPIPE]." It's honestly not super clear, but I assume the problem is similar with seqpacket since it's connection-oriented, or did I miss something? For example in sctp_sendmsg() IIUC we raise a SIGPIPE regardless of whether the socket is STREAM or SEQPACKET. > >Page 1802 (description of 'send()' call): >MSG_NOSIGNAL > >Requests not to send the SIGPIPE signal if an attempt to >send is made on a stream-oriented socket that is no >longer connec...

...r able to send. In addition, the send >> operation fails with the error [EPIPE]." >> >> It's honestly not super clear, but I assume the problem is similar with >> seqpacket since it's connection-oriented, or did I miss something? >> >> For example in sctp_sendmsg() IIUC we raise a SIGPIPE regardless of >> whether the socket is STREAM or SEQPACKET. > >Hm, yes, you're right. Seems check for socket type is not needed in this case, >as this function is only for connection oriented sockets. Ack! > >> >>> >>> Page 1...

...r able to send. In addition, the send >> operation fails with the error [EPIPE]." >> >> It's honestly not super clear, but I assume the problem is similar with >> seqpacket since it's connection-oriented, or did I miss something? >> >> For example in sctp_sendmsg() IIUC we raise a SIGPIPE regardless of >> whether the socket is STREAM or SEQPACKET. > >Update about sending SIGPIPE for SOCK_SEQPACKET, I checked POSIX doc and kernel sources more deeply: > > >1) > >I checked four types of sockets, which sends SIGPIPE for SOCK_SEQPACKET...

...t;> operation fails with the error [EPIPE]." >>>> >>>> It's honestly not super clear, but I assume the problem is similar with >>>> seqpacket since it's connection-oriented, or did I miss something? >>>> >>>> For example in sctp_sendmsg() IIUC we raise a SIGPIPE regardless of >>>> whether the socket is STREAM or SEQPACKET. >>> >>> Hm, yes, you're right. Seems check for socket type is not needed in this case, >>> as this function is only for connection oriented sockets. >> >> A...