Skip to content

Emulate POSIX_SPAWN_CLOEXEC_DEFAULT in fork/exec #79

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

iCharlesHu
Copy link
Contributor

POSIX_SPAWN_CLOEXEC_DEFAULT is only available on Darwin. Emulate POSIX_SPAWN_CLOEXEC_DEFAULT on other platforms by calling close after fork, before exec.

This commit also removes _subprocess_posix_spawn_fallback because we can't emulate POSIX_SPAWN_CLOEXEC_DEFAULT in a thread-safe manner while using posix_spawn.

Resolves: #46

@iCharlesHu iCharlesHu requested review from parkera and itingliu June 13, 2025 22:57
@iCharlesHu iCharlesHu force-pushed the charles/fork-exec-close-fd branch from 6e9afb5 to 3e47e05 Compare June 13, 2025 23:01
@iCharlesHu iCharlesHu force-pushed the charles/fork-exec-close-fd branch from 3e47e05 to 2d9a937 Compare June 13, 2025 23:11
hi = getdtablesize();
}
#else
int hi = 1024;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where does '1024' come from and how safe is it to default to this vs making this #error and requiring a specific implementation for new platforms?

Also, the following additional platforms support getdtablesize: FreeBSD, OpenBSD, NetBSD, Solaris, QNX.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of #error, how about if I just call getdtablesize unconditionally here and have it naturally error on platforms that don't support it.

@lin72h
Copy link

lin72h commented Jun 14, 2025

FreeBSD PR #1698 adds support for POSIX O_CLOFORK, which could simplify this implementation.

@iCharlesHu
Copy link
Contributor Author

FreeBSD PR #1698 adds support for POSIX O_CLOFORK, which could simplify this implementation.

Ahh thanks. Good to know.

char * _Nullable const args[_Nonnull],
char * _Nullable const env[_Nullable],
gid_t * _Nullable process_group_id
int _shims_snprintf(
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need this shim?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On Linux this function isn't exposed via import Glibc

@iCharlesHu iCharlesHu force-pushed the charles/fork-exec-close-fd branch from cd79141 to c217b39 Compare July 3, 2025 04:40
@iCharlesHu
Copy link
Contributor Author

Addressed review comments.

@lin72h
Copy link

lin72h commented Jul 7, 2025

Just a heads up - the PR has merged. I think the timing means it'll likely make it into the upcoming FreeBSD 15 release in December.

Copy link
Contributor

@itingliu itingliu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Linux CI failure looks relevant

[7/22] Compiling CSystem shims.c
/__w/swift-subprocess/swift-subprocess/Sources/_SubprocessCShims/process_shims.c:318:28: error: use of undeclared identifier 'val'
  318 |     if (errno == ERANGE || val <= 0 || val > INT_MAX) {
      |         

&file_actions, file_descriptors[2], STDOUT_FILENO
);
if (rc != 0) { return rc; }
if (errno == ERANGE || val <= 0 || val > INT_MAX) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is what's causing the Linux CI failure

[7/22] Compiling CSystem shims.c
/__w/swift-subprocess/swift-subprocess/Sources/_SubprocessCShims/process_shims.c:318:28: error: use of undeclared identifier 'val'
  318 |     if (errno == ERANGE || val <= 0 || val > INT_MAX) {

Should be value instead?

@ricardobranco777
Copy link

ricardobranco777 commented Jul 26, 2025

Now that O_CLOFORK is merged in all *BSD, work can be started on support O_CLOFORK flags.

POSIX_SPAWN_CLOEXEC_DEFAULT is only available on Darwin. Emulate POSIX_SPAWN_CLOEXEC_DEFAULT on other platforms by calling close after fork, before exec.

This commit also removes _subprocess_posix_spawn_fallback because we can't emulate POSIX_SPAWN_CLOEXEC_DEFAULT in a thread-safe manner while using posix_spawn.
@iCharlesHu iCharlesHu force-pushed the charles/fork-exec-close-fd branch from c217b39 to 769ea70 Compare August 11, 2025 23:42
@iCharlesHu iCharlesHu force-pushed the charles/fork-exec-close-fd branch from 769ea70 to e791d2e Compare August 12, 2025 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fork+exec fails to close other file descriptors
8 participants