[PATCH 1/2] selftests: pid_namespace: Include sys/mount.h

When executing "make -C tools/testing/selftests/pid_namespace", there exist many errors such as: $ make -C tools/testing/selftests/pid_namespace ... pid_max.c:42:15: error: implicit declaration of function 'mount' [-Wimplicit-function-declaration] ... pid_max.c:42:36: error: 'MS_PRIVATE

[PATCH 2/2] selftests: pid_namespace: Skip tests if not root

CLONE_NEWPID or CLONE_NEWNS requires CAP_SYS_ADMIN, if the tests are not running as root, just skip tests rather than fail and also give a warning to the user. Before: $ make -C tools/testing/selftests/pid_namespace $ tools/testing/selftests/pid_namespace/pid_max ... # RUN glob

[PATCH 0/2] Fix compile-time and run-time issues for pid_namespace

Tiezhu Yang (2): selftests: pid_namespace: Include sys/mount.h selftests: pid_namespace: Skip tests if not root tools/testing/selftests/pid_namespace/pid_max.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) -- 2.42.0

RE: [PATCH v3 2/2] x86/sgx: Implement EUPDATESVN and opportunistically call it during first EPC page alloc

> So then why on earth is the kernel implementing automatic updates? I read > back > through most of the cover letters, and IIUC, we went straight from "destroy > all > enclaves and force an update" to "blindly try to do EUPDATESVN every time > the > number of enclaves goes from 0=>1". Those are

[PATCH bpf-next] selftests/bpf: Fix compilation errors

From: Feng Yang If the CONFIG_NET_SCH_BPF configuration is not enabled, the BPF test compilation will report the following error: In file included from progs/bpf_qdisc_fq.c:39: progs/bpf_qdisc_common.h:17:51: error: declaration of 'struct bpf_sk_buff_ptr' will not be visible outside of this func

Re: [RFC PATCH 39/39] KVM: guest_memfd: Dynamically split/reconstruct HugeTLB page

On Fri, Apr 25, 2025 at 03:45:20PM -0700, Ackerley Tng wrote: > Yan Zhao writes: > > > On Thu, Apr 24, 2025 at 11:15:11AM -0700, Ackerley Tng wrote: > >> Vishal Annapurve writes: > >> > >> > On Thu, Apr 24, 2025 at 1:15 AM Yan Zhao wrote: > >> >> > >> >> On Thu, Apr 24, 2025 at 01:55:51PM +080

Re: [PATCH] selftests/mm: use long for dwRegionSize

On Sun, 27 Apr 2025 15:56:39 +0530 Siddarth G wrote: > Change the type of 'dwRegionSize' in wp_init() and wp_free() > from int to long to match callers that pass long or > unsigned long long values. > > wp_addr_range function is left unchanged because it passes > 'dwRegionSize' parameter directl

Re: [PATCH v1 1/7] mfd: stmpe-spi: Correct the name used in MODULE_DEVICE_TABLE

On 26/04/2025 18:16, Alexey Gladkov wrote: > The name used in the macro does not exist. > > drivers/mfd/stmpe-spi.c:132:26: error: use of undeclared identifier 'stmpe_id' > 132 | MODULE_DEVICE_TABLE(spi, stmpe_id); > | ^ > 1 error generated. Reviewed-by: Krzyszto

[PATCH] selftests/mm: use long for dwRegionSize

Change the type of 'dwRegionSize' in wp_init() and wp_free() from int to long to match callers that pass long or unsigned long long values. wp_addr_range function is left unchanged because it passes 'dwRegionSize' parameter directly to pagemap_ioctl, which expects an int. Signed-off-by: Siddarth

[PATCH RESEND] selftests/seccomp: fix syscall_restart test for arm compat

The inconsistencies in the systcall ABI between arm and arm-compat can can cause a failure in the syscall_restart test due to the logic attempting to work around the differences. The 'machine' field for an ARM64 device running in compat mode can report 'armv8l' or 'armv8b' which matches with the st

[PATCH] selftests/seccomp: fix syscall_restart test for arm compat

From: Neill Kapron The inconsistencies in the systcall ABI between arm and arm-compat can can cause a failure in the syscall_restart test due to the logic attempting to work around the differences. The 'machine' field for an ARM64 device running in compat mode can report 'armv8l' or 'armv8b' whic