DerivationBuilder: Preserve death signal across setuid,setgid#15193
Merged
DerivationBuilder: Preserve death signal across setuid,setgid#15193
Conversation
It's apparently a common footgun in Linux that the death signal isn't
preserved across calls to setuid/setgid. If nix-build gets SIGKILL-ed
while a build is running that would lead to a runaway build process that
would get reparented to init/systemd.
This is pretty easy to reproduce with the following derivation:
derivation {
name = "pdeathsig-repro";
system = builtins.currentSystem;
builder = "/bin/sh";
args = [
"-c"
''
while :; do :; done
''
];
}
And the reproduction script:
sudo nix-build repro.nix &
sleep 3
BUILDER=$(pgrep -u nixbld1)
sudo kill -9 $(pgrep -f 'nix-build.*repro')
sleep 1
ps -p $BUILDER -o pid,ppid,user,comm
To address this we have to restore the death signal after all the calls
to setuid/setgid. This is done in a helper function preserveDeathSignal
that takes a callback to avoid code duplication.
See: golang/go#9686
Contributor
Author
|
@edolstra, could you review this one, since you are the most familiar with the sandboxing setup? |
Contributor
Author
|
I'm pretty sure that I saw this happen in a real-world scenario with some build system. |
|
This real-world scenario happened to me and I confirm that I can no longer reproduce it with this patch. Thanks! |
Ericson2314
approved these changes
Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It's apparently a common footgun in Linux that the death signal isn't preserved across calls to setuid/setgid. If nix-build gets SIGKILL-ed while a build is running that would lead to a runaway build process that would get reparented to init/systemd.
This is pretty easy to reproduce with the following derivation:
And the reproduction script:
To address this we have to restore the death signal after all the calls to setuid/setgid. This is done in a helper function preserveDeathSignal that takes a callback to avoid code duplication.
See: golang/go#9686
Motivation
Context
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.