tools/testing/selftests/pid_namespace/regression_enomem.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/pid_namespace/regression_enomem.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/pid_namespace/regression_enomem.c- Extension
.c- Size
- 791 bytes
- Lines
- 45
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: implementation source
- Status
- source implementation candidate
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
assert.herrno.hfcntl.hlinux/types.hsched.hsignal.hstdio.hstdlib.hstring.hsyscall.hsys/wait.hkselftest_harness.h../pidfd/pidfd.h
Detected Declarations
function b26ebfe12f34
Annotated Snippet
#define _GNU_SOURCE
#include <assert.h>
#include <errno.h>
#include <fcntl.h>
#include <linux/types.h>
#include <sched.h>
#include <signal.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <syscall.h>
#include <sys/wait.h>
#include "kselftest_harness.h"
#include "../pidfd/pidfd.h"
/*
* Regression test for:
* 35f71bc0a09a ("fork: report pid reservation failure properly")
* b26ebfe12f34 ("pid: Fix error return value in some cases")
*/
TEST(regression_enomem)
{
pid_t pid;
if (geteuid())
EXPECT_EQ(0, unshare(CLONE_NEWUSER));
EXPECT_EQ(0, unshare(CLONE_NEWPID));
pid = fork();
ASSERT_GE(pid, 0);
if (pid == 0)
exit(EXIT_SUCCESS);
EXPECT_EQ(0, wait_for_pid(pid));
pid = fork();
ASSERT_LT(pid, 0);
ASSERT_EQ(errno, ENOMEM);
}
TEST_HARNESS_MAIN
Annotation
- Immediate include surface: `assert.h`, `errno.h`, `fcntl.h`, `linux/types.h`, `sched.h`, `signal.h`, `stdio.h`, `stdlib.h`.
- Detected declarations: `function b26ebfe12f34`.
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.