- Linux-kselftest-mirror - lists.linaro.org

[REGRESSION] lkft kselftest for next-20220524

by lkft＠linaro.org

## Build * kernel: 5.18.0 * git: ['', 'https://gitlab.com/Linaro/lkft/mirrors/next/linux-next'] * git branch: master * git commit: 09ce5091ff971cdbfd67ad84dc561ea27f10d67a * git describe: next-20220524 * test details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20220524 ## Test Regressions (compared to next-20220520) * dragonboard-410c, kselftest-rtc - rtc.rtctest.rtc.uie_read * dragonboard-845c, kselftest-proc - proc.proc-uptime-001 * qemu_x86_64, kselftest-timers - timers.rtcpie ## Metric Regressions (compared to next-20220520) No metric regressions found. Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Test Fixes (compared to next-20220520) * dragonboard-845c, kselftest-timers - timers.rtcpie * qemu-arm64-gic-version2, kselftest-cgroup - cgroup.test_freezer * qemu-arm64-gic-version3, kselftest-timers - timers.rtcpie * qemu-arm64-mte, kselftest-cgroup - cgroup.test_freezer * qemu_arm, kselftest-pidfd - pidfd.pidfd_poll_test * qemu_arm, kselftest-timers - timers.rtcpie ## Metric Fixes (compared to next-20220520) No metric fixes found. ## Test result summary total: 5813, pass: 3119, fail: 608, skip: 2086, xfail: 0 ## Build Summary ## Test suites summary * kselftest-android * kselftest-arm64 * kselftest-breakpoints * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-drivers * kselftest-efivarfs * kselftest-filesystems * kselftest-firmware * kselftest-fpu * kselftest-futex * kselftest-gpio * kselftest-intel_pstate * kselftest-ipc * kselftest-ir * kselftest-kcmp * kselftest-kexec * kselftest-kvm * kselftest-lib * kselftest-livepatch * kselftest-membarrier * kselftest-memfd * kselftest-memory-hotplug * kselftest-mincore * kselftest-mount * kselftest-mqueue * kselftest-net * kselftest-openat2 * kselftest-pid_namespace * kselftest-pidfd * kselftest-proc * kselftest-pstore * kselftest-ptrace * kselftest-rseq * kselftest-rtc * kselftest-seccomp * kselftest-sigaltstack * kselftest-size * kselftest-splice * kselftest-static_keys * kselftest-sync * kselftest-sysctl * kselftest-timens * kselftest-timers * kselftest-tmpfs * kselftest-tpm2 * kselftest-user * kselftest-vm * kselftest-x86 * kselftest-zram -- Linaro LKFT https://lkft.linaro.org

3 years, 5 months

1
0
0 0

Re: [GIT PULL] KUnit update for Linux 5.19-rc1

by Shuah Khan

On 5/23/22 12:21 PM, Shuah Khan wrote: > Hi Linus, > > Please pull the following KUnit update for Linux 5.19-rc1. > > This KUnit update for Linux 5.19-rc1 consists of several fixes, cleanups, > and enhancements to tests and framework: > > - introduces _NULL and _NOT_NULL macros to pointer error checks > > - reworks kunit_resource allocation policy to fix memory leaks when > caller doesn't specify free() function to be used when allocating > memory using kunit_add_resource() and kunit_alloc_resource() funcs. > > - adds ability to specify suite-level init and exit functions > > diff is attached. > > thanks, > -- Shuah > This bounced from linux-kselftest list as the diff exceeded the message size. Sorry for the noise for others that are seeing this twice (minus the diff). FYI that the following KUnit pull request has been sent for Linux 5.19-rc1 thanks, -- Shuah > ---------------------------------------------------------------- > The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17: > > Linux 5.18-rc1 (2022-04-03 14:08:21 -0700) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest tags/linux-kselftest-kunit-5.19-rc1 > > for you to fetch changes up to e7eaffce47b7db72b077630dbe836f0c4132496d: > > kunit: tool: Use qemu-system-i386 for i386 runs (2022-05-18 17:03:54 -0600) > > ---------------------------------------------------------------- > linux-kselftest-kunit-5.19-rc1 > > This KUnit update for Linux 5.19-rc1 consists of several fixes, cleanups, > and enhancements to tests and framework: > > - introduces _NULL and _NOT_NULL macros to pointer error checks > > - reworks kunit_resource allocation policy to fix memory leaks when > caller doesn't specify free() function to be used when allocating > memory using kunit_add_resource() and kunit_alloc_resource() funcs. > > - adds ability to specify suite-level init and exit functions > > ---------------------------------------------------------------- > Brendan Higgins (2): > kunit: add support for kunit_suites that reference init code > kunit: tool: update riscv QEMU config with new serial dependency > > Daniel Latypov (25): > kunit: tool: make --json handling a bit clearer > kunit: tool: drop unused KernelDirectoryPath var > kunit: tool: drop last uses of collections.namedtuple > kunit: tool: simplify code since build_dir can't be None > kunit: tool: readability tweaks in KernelCI json generation logic > kunit: tool: refactor how we plumb metadata into JSON > kunit: tool: properly report the used arch for --json, or '' if not known > kunit: tool: more descriptive metavars/--help output > kunit: split resource API from test.h into new resource.h > kunit: split resource API impl from test.c into new resource.c > Documentation: kunit: update kconfig options needed for UML coverage > kunit: rename print_subtest_{start,end} for clarity (s/subtest/suite) > kunit: add ability to specify suite-level init and exit functions > kfence: test: use new suite_{init/exit} support, add .kunitconfig > kunit: fix debugfs code to use enum kunit_status, not bool > lib/Kconfig.debug: change KUnit tests to default to KUNIT_ALL_TESTS > kunit: bail out of test filtering logic quicker if OOM > kunit: tool: update test counts summary line format > kunit: tool: stop using a shell to run kernel under QEMU > kunit: tool: print clearer error message when there's no TAP output > kunit: tool: remove dead parse_crash_in_log() logic > kunit: tool: make parser stop overwriting status of suites w/ no_tests > kunit: tool: minor cosmetic cleanups in kunit_parser.py > kunit: tool: misc cleanups > kunit: fix executor OOM error handling logic on non-UML > > David Gow (5): > list: test: Test the hlist structure > kunit: Make kunit_remove_resource() idempotent > kunit: Rework kunit_resource allocation policy > kunit: tool: Add list of all valid test configs on UML > kunit: tool: Use qemu-system-i386 for i386 runs > > Kees Cook (1): > kunit: tool: Do not colorize output when redirected > > Marco Elver (1): > kcsan: test: use new suite_{init,exit} support > > Miguel Ojeda (1): > kunit: take `kunit_assert` as `const` > > Ricardo Ribalda (6): > kunit: Introduce _NULL and _NOT_NULL macros > kunit: use NULL macros > thunderbolt: test: use NULL macros > kasan: test: Use NULL macros > mctp: test: Use NULL macros > apparmor: test: Use NULL macros > > > Documentation/dev-tools/kunit/api/index.rst | 5 + > Documentation/dev-tools/kunit/api/resource.rst | 13 + > Documentation/dev-tools/kunit/running_tips.rst | 3 +- > Documentation/dev-tools/kunit/usage.rst | 19 +- > drivers/thunderbolt/test.c | 134 +++---- > include/kunit/resource.h | 406 ++++++++++++++++++++ > include/kunit/test.h | 418 ++++++--------------- > kernel/kcsan/kcsan_test.c | 31 +- > lib/Kconfig.debug | 15 +- > lib/kunit/Makefile | 1 + > lib/kunit/debugfs.c | 2 +- > lib/kunit/executor.c | 32 +- > lib/kunit/executor_test.c | 4 +- > lib/kunit/kunit-example-test.c | 16 + > lib/kunit/kunit-test.c | 37 +- > lib/kunit/resource.c | 79 ++++ > lib/kunit/test.c | 145 ++----- > lib/list-test.c | 397 ++++++++++++++++++- > lib/test_kasan.c | 2 +- > mm/kfence/.kunitconfig | 6 + > mm/kfence/kfence_test.c | 31 +- > net/mctp/test/route-test.c | 4 +- > security/apparmor/policy_unpack_test.c | 6 +- > tools/testing/kunit/configs/all_tests_uml.config | 37 ++ > tools/testing/kunit/kunit.py | 63 ++-- > tools/testing/kunit/kunit_config.py | 21 +- > tools/testing/kunit/kunit_json.py | 66 ++-- > tools/testing/kunit/kunit_kernel.py | 81 ++-- > tools/testing/kunit/kunit_parser.py | 154 +++----- > tools/testing/kunit/kunit_tool_test.py | 44 +-- > tools/testing/kunit/qemu_config.py | 17 +- > tools/testing/kunit/qemu_configs/alpha.py | 2 +- > tools/testing/kunit/qemu_configs/arm.py | 2 +- > tools/testing/kunit/qemu_configs/arm64.py | 2 +- > tools/testing/kunit/qemu_configs/i386.py | 4 +- > tools/testing/kunit/qemu_configs/powerpc.py | 2 +- > tools/testing/kunit/qemu_configs/riscv.py | 7 +- > tools/testing/kunit/qemu_configs/s390.py | 4 +- > tools/testing/kunit/qemu_configs/sparc.py | 2 +- > tools/testing/kunit/qemu_configs/x86_64.py | 2 +- > tools/testing/kunit/run_checks.py | 2 +- > .../kunit/test_data/test_is_test_passed-crash.log | 70 ---- > .../test_is_test_passed-no_tests_no_plan.log | 2 +- > 43 files changed, 1499 insertions(+), 891 deletions(-) > create mode 100644 Documentation/dev-tools/kunit/api/resource.rst > create mode 100644 include/kunit/resource.h > create mode 100644 lib/kunit/resource.c > create mode 100644 mm/kfence/.kunitconfig > create mode 100644 tools/testing/kunit/configs/all_tests_uml.config > delete mode 100644 tools/testing/kunit/test_data/test_is_test_passed-crash.log > ----------------------------------------------------------------

3 years, 5 months

1
0
0 0

[PATCH v2 0/3] fat: add support for the renameat2 RENAME_EXCHANGE flag

by Javier Martinez Canillas

Hello, This series add support for the renameat2 system call RENAME_EXCHANGE flag (which allows to atomically replace two paths) to the vfat filesystem code. There are many use cases for this, but we are particularly interested in making possible for vfat filesystems to be part of OSTree [0] deployments. Currently OSTree relies on symbolic links to make the deployment updates an atomic transactional operation. But RENAME_EXCHANGE could be used [1] to achieve a similar level of robustness when using a vfat filesystem. Patch #1 is just a preparatory patch to introduce the RENAME_EXCHANGE support in patch #2 and finally patch #3 adds some kselftests to test it. This is a v2 that addresses issues pointed out in the first version that was posted as an RFC: https://lore.kernel.org/lkml/20220519092343.2776414-1-javierm@redhat.com/ [0]: https://github.com/ostreedev/ostree [1]: https://github.com/ostreedev/ostree/issues/1649 Changes in v2: - Only update the new_dir inode version and timestamps if != old_dir (Alex Larsson). - Add some helper functions to avoid duplicating code (OGAWA Hirofumi). - Use braces for multi-lines blocks even if are one statement (OGAWA Hirofumi). - Mention in commit message that the operation is as transactional as possible but within the vfat limitations of not having a journal (Colin Walters). - Call sync to flush the page cache before checking the file contents (Alex Larsson). - Drop RFC prefix since the patches already got some review. Javier Martinez Canillas (3): fat: add a vfat_rename2() and make existing .rename callback a helper fat: add renameat2 RENAME_EXCHANGE flag support selftests/filesystems: add a vfat RENAME_EXCHANGE test MAINTAINERS | 1 + fs/fat/namei_vfat.c | 193 +++++++++++++++++- tools/testing/selftests/Makefile | 1 + .../selftests/filesystems/fat/Makefile | 7 + .../testing/selftests/filesystems/fat/config | 2 + .../filesystems/fat/rename_exchange.c | 37 ++++ .../filesystems/fat/run_fat_tests.sh | 82 ++++++++ 7 files changed, 316 insertions(+), 7 deletions(-) create mode 100644 tools/testing/selftests/filesystems/fat/Makefile create mode 100644 tools/testing/selftests/filesystems/fat/config create mode 100644 tools/testing/selftests/filesystems/fat/rename_exchange.c create mode 100755 tools/testing/selftests/filesystems/fat/run_fat_tests.sh -- 2.36.1

3 years, 5 months

2
3
0 0

[PATCH] selftests/powerpc/pmu: fix spelling mistake "mis-match" -> "mismatch"

by Colin Ian King

There are a few spelling mistakes in error messages. Fix them. Signed-off-by: Colin Ian King <colin.i.king(a)gmail.com> --- tools/testing/selftests/powerpc/security/spectre_v2.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/testing/selftests/powerpc/security/spectre_v2.c b/tools/testing/selftests/powerpc/security/spectre_v2.c index d42ca8c676c3..e832605442bb 100644 --- a/tools/testing/selftests/powerpc/security/spectre_v2.c +++ b/tools/testing/selftests/powerpc/security/spectre_v2.c @@ -183,7 +183,7 @@ int spectre_v2_test(void) // These should all not affect userspace branch prediction if (miss_percent > 15) { printf("Branch misses > 15%% unexpected in this configuration!\n"); - printf("Possible mis-match between reported & actual mitigation\n"); + printf("Possible mismatch between reported & actual mitigation\n"); /* * Such a mismatch may be caused by a guest system * reporting as vulnerable when the host is mitigated. @@ -201,14 +201,14 @@ int spectre_v2_test(void) // This seems to affect userspace branch prediction a bit? if (miss_percent > 25) { printf("Branch misses > 25%% unexpected in this configuration!\n"); - printf("Possible mis-match between reported & actual mitigation\n"); + printf("Possible mismatch between reported & actual mitigation\n"); return 1; } break; case COUNT_CACHE_DISABLED: if (miss_percent < 95) { printf("Branch misses < 20%% unexpected in this configuration!\n"); - printf("Possible mis-match between reported & actual mitigation\n"); + printf("Possible mismatch between reported & actual mitigation\n"); return 1; } break; -- 2.35.1

3 years, 5 months

2
1
0 0

[PATCH] selftest/powerpc/pmu/ebb: remove fixed_instruction.S

by Madhavan Srinivasan

Commit 3752e453f6ba ("selftests/powerpc: Add tests of PMU EBBs") added selftest testcases to verify EBB interface. instruction_count_test.c testcase needs a fixed loop function to count overhead. Instead of using the thirty_two_instruction_loop() in fixed_instruction_loop.S in ebb folder, file is linked with thirty_two_instruction_loop() in loop.S from top folder. Since fixed_instruction_loop.S not used, patch removes the file. Signed-off-by: Madhavan Srinivasan <maddy(a)linux.ibm.com> --- .../powerpc/pmu/ebb/fixed_instruction_loop.S | 43 ------------------- 1 file changed, 43 deletions(-) delete mode 100644 tools/testing/selftests/powerpc/pmu/ebb/fixed_instruction_loop.S diff --git a/tools/testing/selftests/powerpc/pmu/ebb/fixed_instruction_loop.S b/tools/testing/selftests/powerpc/pmu/ebb/fixed_instruction_loop.S deleted file mode 100644 index 08a7b5f133b9..000000000000 --- a/tools/testing/selftests/powerpc/pmu/ebb/fixed_instruction_loop.S +++ /dev/null @@ -1,43 +0,0 @@ -/* SPDX-License-Identifier: GPL-2.0-only */ -/* - * Copyright 2014, Michael Ellerman, IBM Corp. - */ - -#include <ppc-asm.h> - - .text - -FUNC_START(thirty_two_instruction_loop) - cmpwi r3,0 - beqlr - addi r4,r3,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 - addi r4,r4,1 # 28 addi's - subi r3,r3,1 - b FUNC_NAME(thirty_two_instruction_loop) -FUNC_END(thirty_two_instruction_loop) -- 2.34.1

3 years, 5 months

2
1
0 0

[REGRESSION] lkft kselftest for next-20220523

by lkft＠linaro.org

## Build * kernel: 5.18.0 * git: ['', 'https://gitlab.com/Linaro/lkft/mirrors/next/linux-next'] * git branch: master * git commit: cc63e8e92cb872081f249ea16e6c460642f3e4fb * git describe: next-20220523 * test details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20220523 ## Test Regressions (compared to next-20220520) * dragonboard-845c, kselftest-cgroup - cgroup.test_freezer - cgroup.test_freezer.test_cgfreezer_ptrace * dragonboard-845c, kselftest-rtc - rtc.rtctest.rtc.uie_select ## Metric Regressions (compared to next-20220520) No metric regressions found. Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Test Fixes (compared to next-20220520) * dragonboard-845c, kselftest-timers - timers.rtcpie * qemu-arm64-gic-version2, kselftest-cgroup - cgroup.test_freezer * qemu-arm64-gic-version2, kselftest-timers - timers.rtcpie * qemu-arm64-gic-version3, kselftest-timers - timers.rtcpie * qemu-arm64-mte, kselftest-cgroup - cgroup.test_freezer * qemu-arm64-mte, kselftest-timers - timers.rtcpie * qemu_arm, kselftest-timers - timers.rtcpie * qemu_arm64, kselftest-timers - timers.rtcpie ## Metric Fixes (compared to next-20220520) No metric fixes found. ## Test result summary total: 5547, pass: 2993, fail: 526, skip: 2028, xfail: 0 ## Build Summary ## Test suites summary * kselftest-android * kselftest-arm64 * kselftest-breakpoints * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-drivers * kselftest-efivarfs * kselftest-filesystems * kselftest-firmware * kselftest-fpu * kselftest-futex * kselftest-gpio * kselftest-intel_pstate * kselftest-ipc * kselftest-ir * kselftest-kcmp * kselftest-kexec * kselftest-kvm * kselftest-lib * kselftest-livepatch * kselftest-membarrier * kselftest-memfd * kselftest-memory-hotplug * kselftest-mincore * kselftest-mount * kselftest-mqueue * kselftest-net * kselftest-openat2 * kselftest-pid_namespace * kselftest-pidfd * kselftest-proc * kselftest-pstore * kselftest-ptrace * kselftest-rseq * kselftest-rtc * kselftest-seccomp * kselftest-sigaltstack * kselftest-size * kselftest-splice * kselftest-static_keys * kselftest-sync * kselftest-sysctl * kselftest-timens * kselftest-timers * kselftest-tmpfs * kselftest-tpm2 * kselftest-user * kselftest-vm * kselftest-x86 * kselftest-zram -- Linaro LKFT https://lkft.linaro.org

3 years, 5 months

1
0
0 0

Napływ Klientów ze strony

by "Mikołaj Rudzik"

Dzień dobry, chciałbym poinformować Państwa o możliwości pozyskania nowych zleceń ze strony www. Widzimy zainteresowanie potencjalnych Klientów Państwa firmą, dlatego chętnie pomożemy Państwu dotrzeć z ofertą do większego grona odbiorców poprzez efektywne metody pozycjonowania strony w Google. Czy mógłbym liczyć na kontakt zwrotny? Pozdrawiam, Mikołaj Rudzik

3 years, 5 months

1
0
0 0

[PATCH bpf-next 0/4] bpf: verifier: remove redundant opcode checks

by Shung-Hsi Yu

This patch set aims to remove opcode checks in BPF verifier that have become redundant since commit 5e581dad4fec ("bpf: make unknown opcode handling more robust"), either remove them entirely, or turn them into comments in places where the redundancy may not be clear. The exceptions here are opcode check for BPF_LD_{ABS,IND} and BPF_JMP_{JA,CALL,EXIT}; they cover opcode validation not done in bpf_opcode_in_insntable() so is not removed. After apply the patch set test_verifier passes and does not need further modification: Summary: 1348 PASSED, 635 SKIPPED, 0 FAILED Also, add comments at places that I find confusing while working on the removal, namely: 1. resolve_pseudo_ldimm64() also validates opcode 2. BPF_SIZE check in check_ld_imm() guards against JMP to the 2nd BPF_LD_IMM64 instruction 3. reason behind why ld_imm64 test cases should be rejected by the verifier Shung-Hsi Yu (4): bpf: verifier: update resolve_pseudo_ldimm64() comment bpf: verifier: explain opcode check in check_ld_imm() bpf: verifier: remove redundant opcode checks selftests/bpf: add reason of rejection in ld_imm64 kernel/bpf/verifier.c | 33 ++++++++----------- .../testing/selftests/bpf/verifier/ld_imm64.c | 20 ++++++----- 2 files changed, 25 insertions(+), 28 deletions(-) base-commit: 68084a13642001b73aade05819584f18945f3297 -- 2.36.1

3 years, 5 months

2
3
0 0

[PATCH][next] selftests/bpf: Fix spelling mistake: "unpriviliged" -> "unprivileged"

by Colin Ian King

There are spelling mistakes in ASSERT messages. Fix these. Signed-off-by: Colin Ian King <colin.i.king(a)gmail.com> --- tools/testing/selftests/bpf/prog_tests/unpriv_bpf_disabled.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/testing/selftests/bpf/prog_tests/unpriv_bpf_disabled.c b/tools/testing/selftests/bpf/prog_tests/unpriv_bpf_disabled.c index 2800185179cf..1ed3cc2092db 100644 --- a/tools/testing/selftests/bpf/prog_tests/unpriv_bpf_disabled.c +++ b/tools/testing/selftests/bpf/prog_tests/unpriv_bpf_disabled.c @@ -261,10 +261,10 @@ void test_unpriv_bpf_disabled(void) if (ret == -EPERM) { /* if unprivileged_bpf_disabled=1, we get -EPERM back; that's okay. */ if (!ASSERT_OK(strcmp(unprivileged_bpf_disabled_orig, "1"), - "unpriviliged_bpf_disabled_on")) + "unprivileged_bpf_disabled_on")) goto cleanup; } else { - if (!ASSERT_OK(ret, "set unpriviliged_bpf_disabled")) + if (!ASSERT_OK(ret, "set unprivileged_bpf_disabled")) goto cleanup; } -- 2.35.3

3 years, 5 months

2
1
0 0

[PATCH] cgroup: Fix an error handling path in alloc_pagecache_max_30M()

by Christophe JAILLET

If the first goto is taken, 'fd' is not opened yet (and is un-initialized). So a direct return is safer. Fixes: c1a31a2f7a9c ("cgroup: fix racy check in alloc_pagecache_max_30M() helper function") Signed-off-by: Christophe JAILLET <christophe.jaillet(a)wanadoo.fr> --- tools/testing/selftests/cgroup/test_memcontrol.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/cgroup/test_memcontrol.c b/tools/testing/selftests/cgroup/test_memcontrol.c index c3d0d5f7b19c..8833359556f3 100644 --- a/tools/testing/selftests/cgroup/test_memcontrol.c +++ b/tools/testing/selftests/cgroup/test_memcontrol.c @@ -448,7 +448,7 @@ static int alloc_pagecache_max_30M(const char *cgroup, void *arg) high = cg_read_long(cgroup, "memory.high"); max = cg_read_long(cgroup, "memory.max"); if (high != MB(30) && max != MB(30)) - goto cleanup; + return -1; fd = get_temp_fd(); if (fd < 0) -- 2.34.1

3 years, 5 months

3
2
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-kselftest-mirror