net: socketpair: fcntl non-functional with socketpair-provided sockets on posix arch #54996
Labels
area: native port
Host native arch port (native_sim)
area: Networking
area: POSIX
POSIX API Library
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Describe the bug
Encountered in #54747,
fcntl()
does not seem to be working onsocketpair()
-provided sockets withCONFIG_ARCH_POSIX
.The result is that non-blocking I/O on
socketpair()
-provided sockets are non-functional (but only onnative_posix
and relatedARCH_POSIX
boards).Please also mention any information which could help others to understand
the problem you're facing:
native_posix
,native_posix_64
,nrf52_bsim
.native_posix
originally because we were linking it in from the native libc. If there was a regression, then it was caused by the massive workaround for splitting networking off to run undernative_posix
and makingCONFIG_ARCH_POSIX
andCONFIG_POSIX_API
mutually exclusive. But that in itself was just fixing issues with which code paths were actually linked-in (i.e. not mixing native posix and zephyr system calls).To Reproduce
Steps to reproduce the behavior:
ztest_test_skip()
added in tests: net: socketpair: clean up tests and provide coverage for all libcs #54747west build -p auto -b native_posix tests/net/sockets/socketpair
Expected behavior
Test cases should pass and non-blocking I/O on socketpair sockets under
native_posix
should be supported.Impact
Non-blocking I/O on socketpair sockets under
native_posix
are not supported until this is fixed.In the larger scope, this is just one of many issues that need to be fixed to support
CONFIG_POSIX_API
underCONFIG_ARCH_POSIX
.Logs and console output
Environment (please complete the following information):
Additional context
This is one of many other conflicts that exist between
CONFIG_ARCH_POSIX
andCONFIG_POSIX_API
and should be addressed along with LTSv3 RoadMap.Also,
socketpair()
will be continue to be marked as experimental until it is stable onnative_posix
.The text was updated successfully, but these errors were encountered: