Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOCK_SEQPACKET is unusable #7153

Closed
vicuna opened this issue Feb 20, 2016 · 1 comment
Closed

SOCK_SEQPACKET is unusable #7153

vicuna opened this issue Feb 20, 2016 · 1 comment

Comments

@vicuna
Copy link

vicuna commented Feb 20, 2016

Original bug ID: 7153
Reporter: mwm
Status: closed (set by @xavierleroy on 2017-09-24T15:33:02Z)
Resolution: fixed
Priority: normal
Severity: tweak
Version: 4.02.3
Target version: 4.04.0 +dev / +beta1 / +beta2
Fixed in version: 4.04.0 +dev / +beta1 / +beta2
Category: otherlibs

Bug description

While the Unix library exports the SOCK_SEQPACKET connction type, it fails to export anything allowing it to be used. In particular, the message flag MSG_EOR (used to mark and detect the end of a packet) isn't there. Worse yet, there's apparently no API for reading from a socket that lets you check the message flags for MSG_EOR (or I couldn't find it, in which case the documentation might be improved).

Given that the SEQPACKET connection type isn't widely implemented, and may only be supported for odd protocol families, possibly the best solution is to simply remove it.

Steps to reproduce

Read the documentation on the Unix library.

@vicuna
Copy link
Author

vicuna commented Jun 29, 2016

Comment author: @xavierleroy

Documented the issue, commit [trunk 4515477]. We could improve support for SOCK_SEQPACKET by binding the recvmsg() and sendmsg() system calls. But it's probably not worth the effort.

@vicuna vicuna closed this as completed Sep 24, 2017
@vicuna vicuna added this to the 4.04.0 milestone Mar 14, 2019
@vicuna vicuna added the bug label Mar 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant