July 2022 - Linux-kselftest-mirror

[PATCH 1/4] kunit: string-stream: Simplify resource use

by Daniel Latypov

From: David Gow <davidgow(a)google.com> Currently, KUnit's string streams are themselves "KUnit resources". This is redundant since the stream itself is already allocated with kunit_kzalloc() and will thus be freed automatically at the end of the test. string-stream is only used internally within KUnit, and isn't using the extra features that resources provide like reference counting, being able to locate them dynamically as "test-local variables", etc. Indeed, the resource's refcount is never incremented when the pointer is returned. The fact that it's always manually destroyed is more evidence that the reference counting is unused. Signed-off-by: David Gow <davidgow(a)google.com> Signed-off-by: Daniel Latypov <dlatypov(a)google.com> --- lib/kunit/string-stream.c | 90 +++++++-------------------------------- lib/kunit/string-stream.h | 2 +- lib/kunit/test.c | 2 +- 3 files changed, 18 insertions(+), 76 deletions(-) diff --git a/lib/kunit/string-stream.c b/lib/kunit/string-stream.c index 141789ca8949..a2496abef152 100644 --- a/lib/kunit/string-stream.c +++ b/lib/kunit/string-stream.c @@ -12,64 +12,31 @@ #include "string-stream.h" -struct string_stream_fragment_alloc_context { - struct kunit *test; - int len; - gfp_t gfp; -}; -static int string_stream_fragment_init(struct kunit_resource *res, - void *context) +static struct string_stream_fragment *alloc_string_stream_fragment( + struct kunit *test, int len, gfp_t gfp) { - struct string_stream_fragment_alloc_context *ctx = context; struct string_stream_fragment *frag; - frag = kunit_kzalloc(ctx->test, sizeof(*frag), ctx->gfp); + frag = kunit_kzalloc(test, sizeof(*frag), gfp); if (!frag) - return -ENOMEM; + return ERR_PTR(-ENOMEM); - frag->test = ctx->test; - frag->fragment = kunit_kmalloc(ctx->test, ctx->len, ctx->gfp); + frag->test = test; + frag->fragment = kunit_kmalloc(test, len, gfp); if (!frag->fragment) - return -ENOMEM; + return ERR_PTR(-ENOMEM); - res->data = frag; - - return 0; + return frag; } -static void string_stream_fragment_free(struct kunit_resource *res) +static void string_stream_fragment_destroy(struct string_stream_fragment *frag) { - struct string_stream_fragment *frag = res->data; - list_del(&frag->node); kunit_kfree(frag->test, frag->fragment); kunit_kfree(frag->test, frag); } -static struct string_stream_fragment *alloc_string_stream_fragment( - struct kunit *test, int len, gfp_t gfp) -{ - struct string_stream_fragment_alloc_context context = { - .test = test, - .len = len, - .gfp = gfp - }; - - return kunit_alloc_resource(test, - string_stream_fragment_init, - string_stream_fragment_free, - gfp, - &context); -} - -static int string_stream_fragment_destroy(struct string_stream_fragment *frag) -{ - return kunit_destroy_resource(frag->test, - kunit_resource_instance_match, - frag); -} - int string_stream_vadd(struct string_stream *stream, const char *fmt, va_list args) @@ -169,48 +136,23 @@ struct string_stream_alloc_context { gfp_t gfp; }; -static int string_stream_init(struct kunit_resource *res, void *context) +struct string_stream *alloc_string_stream(struct kunit *test, gfp_t gfp) { struct string_stream *stream; - struct string_stream_alloc_context *ctx = context; - stream = kunit_kzalloc(ctx->test, sizeof(*stream), ctx->gfp); + stream = kunit_kzalloc(test, sizeof(*stream), gfp); if (!stream) - return -ENOMEM; + return ERR_PTR(-ENOMEM); - res->data = stream; - stream->gfp = ctx->gfp; - stream->test = ctx->test; + stream->gfp = gfp; + stream->test = test; INIT_LIST_HEAD(&stream->fragments); spin_lock_init(&stream->lock); - return 0; + return stream; } -static void string_stream_free(struct kunit_resource *res) +void string_stream_destroy(struct string_stream *stream) { - struct string_stream *stream = res->data; - string_stream_clear(stream); } - -struct string_stream *alloc_string_stream(struct kunit *test, gfp_t gfp) -{ - struct string_stream_alloc_context context = { - .test = test, - .gfp = gfp - }; - - return kunit_alloc_resource(test, - string_stream_init, - string_stream_free, - gfp, - &context); -} - -int string_stream_destroy(struct string_stream *stream) -{ - return kunit_destroy_resource(stream->test, - kunit_resource_instance_match, - stream); -} diff --git a/lib/kunit/string-stream.h b/lib/kunit/string-stream.h index 43f9508a55b4..494dee0f24bd 100644 --- a/lib/kunit/string-stream.h +++ b/lib/kunit/string-stream.h @@ -46,6 +46,6 @@ int string_stream_append(struct string_stream *stream, bool string_stream_is_empty(struct string_stream *stream); -int string_stream_destroy(struct string_stream *stream); +void string_stream_destroy(struct string_stream *stream); #endif /* _KUNIT_STRING_STREAM_H */ diff --git a/lib/kunit/test.c b/lib/kunit/test.c index b73d5bb5c473..0fb2771ca03e 100644 --- a/lib/kunit/test.c +++ b/lib/kunit/test.c @@ -267,7 +267,7 @@ static void kunit_fail(struct kunit *test, const struct kunit_loc *loc, kunit_print_string_stream(test, stream); - WARN_ON(string_stream_destroy(stream)); + string_stream_destroy(stream); } static void __noreturn kunit_abort(struct kunit *test) base-commit: 94681e289bf5d10c9db9db143d1a22d8717205c5 -- 2.37.1.359.gd136c6c3e2-goog

2 years, 5 months

2
7
0 0

[PATCH] selftests/vm: silence uninitialized variable warning

by Dan Carpenter

This code just reads from memory without caring about the data itself. However static checkers complain that "tmp" is never properly initialized. Initialize it to zero and change the name to "dummy" to show that we don't care about the value stored in it. Fixes: c4b6cb884011 ("selftests/vm: add hugetlb madvise MADV_DONTNEED MADV_REMOVE test") Signed-off-by: Dan Carpenter <dan.carpenter(a)oracle.com> --- tools/testing/selftests/vm/hugetlb-madvise.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tools/testing/selftests/vm/hugetlb-madvise.c b/tools/testing/selftests/vm/hugetlb-madvise.c index 6c6af40f5747..3c9943131881 100644 --- a/tools/testing/selftests/vm/hugetlb-madvise.c +++ b/tools/testing/selftests/vm/hugetlb-madvise.c @@ -89,10 +89,11 @@ void write_fault_pages(void *addr, unsigned long nr_pages) void read_fault_pages(void *addr, unsigned long nr_pages) { - unsigned long i, tmp; + unsigned long dummy = 0; + unsigned long i; for (i = 0; i < nr_pages; i++) - tmp += *((unsigned long *)(addr + (i * huge_page_size))); + dummy += *((unsigned long *)(addr + (i * huge_page_size))); } int main(int argc, char **argv) -- 2.35.1

2 years, 5 months

3
4
0 0

Re: linux-next: Tree for Jul 21 (mmc/host & KUNIT)

by Randy Dunlap

On 7/21/22 04:02, Stephen Rothwell wrote: > Hi all, > > Changes since 20220720: > on i386: ld: drivers/mmc/host/sdhci-of-aspeed.o: in function `aspeed_sdhci_phase_ddr52': sdhci-of-aspeed.c:(.text+0x2a2): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x2c5): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x2ea): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x30d): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x333): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x35a): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x380): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x3a7): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x3cd): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x3f4): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x41a): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x441): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x467): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x48e): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x4b4): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x4db): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x501): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x528): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x54e): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x575): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x59b): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x5c2): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x5e8): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x60f): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x635): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x65c): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x682): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x6a9): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x6cf): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x6f6): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x71c): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x743): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x769): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x790): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x7b6): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x7dd): undefined reference to `kunit_do_failed_assertion' ld: drivers/mmc/host/sdhci-of-aspeed.o: in function `aspeed_sdhci_phase_hs200': sdhci-of-aspeed.c:(.text+0x816): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x839): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x85e): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x881): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x8a7): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x8ce): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x8f4): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x91b): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x941): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x968): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x98e): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0x9b5): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0x9db): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0xa02): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0xa28): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0xa4f): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0xa75): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0xa9c): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0xac2): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0xae9): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0xb0f): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0xb36): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0xb5c): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0xb83): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0xba9): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0xbd0): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0xbf6): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0xc1d): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0xc43): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0xc6a): undefined reference to `kunit_do_failed_assertion' ld: sdhci-of-aspeed.c:(.text+0xc90): undefined reference to `kunit_binary_assert_format' ld: sdhci-of-aspeed.c:(.text+0xcb7): undefined reference to `kunit_do_failed_assertion' Full randconfig file is attached. -- ~Randy

2 years, 5 months

2
1
0 0

[PATCH v2] Documentation: kunit: Add CLI args for kunit_tool

by Sadiya Kazi

Run_wrapper.rst was missing some command line arguments. Added additional args in the file. Signed-off-by: Sadiya Kazi <sadiyakazi(a)google.com> --- Changes since V1: https://lore.kernel.org/linux-kselftest/20220719092214.995965-1-sadiyakazi@… - Addressed most of the review comments from Maira and David, except removing the duplicate arguments as I felt its worth keeping them in the reference documentation as well as in context. We can improve them and differentiate their use cases in the future patches. --- Documentation/dev-tools/kunit/run_wrapper.rst | 60 ++++++++++++++++++- 1 file changed, 59 insertions(+), 1 deletion(-) diff --git a/Documentation/dev-tools/kunit/run_wrapper.rst b/Documentation/dev-tools/kunit/run_wrapper.rst index 5e560f2c5fca..600af7ac5f88 100644 --- a/Documentation/dev-tools/kunit/run_wrapper.rst +++ b/Documentation/dev-tools/kunit/run_wrapper.rst @@ -233,7 +233,7 @@ Command-Line Arguments ====================== kunit_tool has a number of other command-line arguments which can -be useful for our test environment. Below the most commonly used +be useful for our test environment. Below are the most commonly used command line arguments: - ``--help``: Lists all available options. To list common options, @@ -257,3 +257,61 @@ command line arguments: added or modified. Instead, enable all tests which have satisfied dependencies by adding ``CONFIG_KUNIT_ALL_TESTS=y`` to your ``.kunitconfig``. + +- ``--kunitconfig``: Specifies the path or the directory of the ``.kunitconfig`` + file. For example: + + - ``lib/kunit/.kunitconfig`` can be the path of the file. + + - ``lib/kunit`` can be the directory in which the file is located. + + This file is used to build and run with a predefined set of tests + and their dependencies. For example, to run tests for a given subsystem. + +- ``--kconfig_add``: Specifies additional configuration options to be + appended to the ``.kunitconfig`` file. + For example, ``./tools/testing/kunit/kunit.py run --kconfig_add CONFIG_KASAN=y``. + +- ``--arch``: Runs tests on the specified architecture. The architecture + specified must match the Kbuild ARCH environment variable. + For example, i386, x86_64, arm, um, etc. Non-UML architectures run on QEMU. + Default is `um`. + +- ``--cross_compile``: Specifies the Kbuild toolchain. It passes the + same argument as passed to the ``CROSS_COMPILE`` variable used by + Kbuild. This will be the prefix for the toolchain + binaries such as GCC. For example: + + - ``sparc64-linux-gnu-`` if we have the sparc toolchain installed on + our system. + + - ``$HOME/toolchains/microblaze/gcc-9.2.0-nolibc/microblaze-linux/bin/microblaze-linux`` + if we have downloaded the microblaze toolchain from the 0-day + website to a specified path in our home directory called toolchains. + +- ``--qemu_config``: Specifies the path to a file containing a + custom qemu architecture definition. This should be a python file + containing a `QemuArchParams` object. + +- ``--qemu_args``: Specifies additional QEMU arguments, for example, "-smp 8". + +- ``--jobs``: Specifies the number of jobs (commands) to run simultaneously. + By default, this is set to the number of cores on your system. + +- ``--timeout``: Specifies the maximum number of seconds allowed for all tests to run. + This does not include the time taken to build the tests. + +- ``--kernel_args``: Specifies additional kernel command-line arguments. Might be repeated. + +- ``--run_isolated``: If set, boots the kernel for each individual suite/test. + This is useful for debugging a non-hermetic test, one that + might pass/fail based on what ran before it. + +- ``--raw_output``: If set, generates unformatted output from kernel. Possible options are: + + - ``all``: To view the full kernel output, use ``--raw_output=all``. + + - ``kunit``: This is the default option and filters to KUnit output. Use ``--raw_output`` or ``--raw_output=kunit``. + +- ``--json``: If set, stores the test results in a JSON format and prints to `stdout` or + saves to a file if a filename is specified. -- 2.37.0.170.g444d1eabd0-goog

2 years, 5 months

5
5
0 0

[RFC V2 PATCH 0/8] selftests: KVM: selftests for fd-based approach of supporting private memory

by Vishal Annapurve

This v2 series implements selftests targeting the feature floated by Chao via: https://lore.kernel.org/linux-mm/20220310140911.50924-1-chao.p.peng@linux.i… Below changes aim to test the fd based approach for guest private memory in context of normal (non-confidential) VMs executing on non-confidential platforms. priv_memfd_test.c file adds a suite of selftests to access private memory from the guest via private/shared accesses and checking if the contents can be leaked to/accessed by vmm via shared memory view. Updates in V2: 1) Tests are added to exercise implicit/explicit memory conversion paths. 2) Test is added to exercise UPM feature without double memory allocation. This series has dependency on following patches: 1) V5 series patches from Chao mentioned above. 2) https://github.com/vishals4gh/linux/commit/b9adedf777ad84af39042e9c19899600… - Fixes host kernel crash with current implementation 3) https://github.com/vishals4gh/linux/commit/0577e351ee36d52c1f6cdcb1b8de7aa6… - Confidential platforms along with the confidentiality aware software stack support a notion of private/shared accesses from the confidential VMs. Generally, a bit in the GPA conveys the shared/private-ness of the access. Non-confidential platforms don't have a notion of private or shared accesses from the guest VMs. To support this notion, KVM_HC_MAP_GPA_RANGE is modified to allow marking an access from a VM within a GPA range as always shared or private. There is an ongoing discussion about adding support for software-only confidential VMs, which should replace this patch. 4) https://github.com/vishals4gh/linux/commit/8d46aea9a7d72e4b1b998066ce0dde08… - Temporary placeholder to be able to test memory conversion paths till the memory conversion exit error code is finalized. 5) https://github.com/vishals4gh/linux/commit/4c36706477c62d9416d635fa6ac4ef64… - Fixes GFN calculation during memory conversion path. Github link for the patches posted as part of this series: https://github.com/vishals4gh/linux/commits/priv_memfd_selftests_rfc_v2 Austin Diviness (1): selftests: kvm: Add hugepage support to priv_memfd_test suite. Vishal Annapurve (7): selftests: kvm: Fix inline assembly for hypercall selftests: kvm: Add a basic selftest to test private memory selftests: kvm: priv_memfd_test: Add support for memory conversion selftests: kvm: priv_memfd_test: Add shared access test selftests: kvm: Add implicit memory conversion tests selftests: kvm: Add KVM_HC_MAP_GPA_RANGE hypercall test selftests: kvm: priv_memfd: Add test avoiding double allocation tools/testing/selftests/kvm/Makefile | 1 + .../selftests/kvm/lib/x86_64/processor.c | 2 +- tools/testing/selftests/kvm/priv_memfd_test.c | 1359 +++++++++++++++++ 3 files changed, 1361 insertions(+), 1 deletion(-) create mode 100644 tools/testing/selftests/kvm/priv_memfd_test.c -- 2.36.0.512.ge40c2bad7a-goog

2 years, 5 months

3
23
0 0

[PATCH v1 0/3] arm64/sve: Document our actual SVE syscall ABI

by Mark Brown

Currently our SVE syscall ABI documentation does not reflect the actual implemented ABI, it says that register state not shared with FPSIMD becomes undefined on syscall when in reality we always clear it. Since changing this would cause a change in the observed kernel behaviour there is a substantial desire to avoid taking advantage of the documented ABI so instead let's document what we actually do so it's clear that it is in reality an ABI. There has been some pushback on tightening the documentation in the past but it is hard to see who that helps, it makes the implementation decisions less clear and makes it harder for people to discover and make use of the actual ABI. The main practical concern is that qemu's user mode does not currently flush the registers. Mark Brown (3): kselftest/arm64: Correct buffer allocation for SVE Z registers arm64/sve: Document our actual ABI for clearing registers on syscall kselftest/arm64: Enforce actual ABI for SVE syscalls Documentation/arm64/sve.rst | 2 +- .../testing/selftests/arm64/abi/syscall-abi.c | 61 ++++++++++++------- 2 files changed, 41 insertions(+), 22 deletions(-) base-commit: a111daf0c53ae91e71fd2bfe7497862d14132e3e -- 2.30.2

2 years, 5 months

2
4
0 0

[REGRESSION] lkft kselftest for next-20220721

by lkft＠linaro.org

## Build * kernel: 5.19.0-rc7 * git: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next * git branch: master * git commit: a3fd3ca134d9485a0f9a7bdcffd7f8bae27f79d3 * git describe: next-20220721 * test details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20220721 ## Test Regressions (compared to v5.19-rc6-12429-g4ee7eaa411ee) * qemu_arm, kselftest-rtc - rtc.rtctest - rtc.rtctest.rtc.date_read_loop ## Metric Regressions (compared to v5.19-rc6-12429-g4ee7eaa411ee) No metric regressions found. Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Test Fixes (compared to v5.19-rc6-12429-g4ee7eaa411ee) * qemu_arm, kselftest-seccomp - seccomp.seccomp_benchmark ## Metric Fixes (compared to v5.19-rc6-12429-g4ee7eaa411ee) No metric fixes found. ## Test result summary total: 345, pass: 167, fail: 44, skip: 134, xfail: 0 ## Build Summary ## Test suites summary * kselftest-android * kselftest-breakpoints * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-drivers-dma-buf * kselftest-efivarfs * kselftest-filesystems * kselftest-filesystems-binderfs * kselftest-firmware * kselftest-fpu * kselftest-gpio * kselftest-ipc * kselftest-ir * kselftest-kcmp * kselftest-lib * kselftest-membarrier * kselftest-netfilter * kselftest-nsfs * kselftest-openat2 * kselftest-pid_namespace * kselftest-pidfd * kselftest-proc * kselftest-pstore * kselftest-rseq * kselftest-rtc * kselftest-seccomp * kselftest-sigaltstack * kselftest-size * kselftest-splice * kselftest-static_keys * kselftest-sync * kselftest-sysctl * kselftest-tc-testing * kselftest-timens * kselftest-timers * kselftest-tmpfs * kselftest-tpm2 * kselftest-user * kselftest-vm -- Linaro LKFT https://lkft.linaro.org

2 years, 5 months

1
0
0 0

[PATCH][next] KVM: selftests: Fix spelling mistake "mismtach" -> "mismatch"

by Colin Ian King

There is a spelling mistake in an assert message. Fix it. Signed-off-by: Colin Ian King <colin.i.king(a)gmail.com> --- tools/testing/selftests/kvm/x86_64/cpuid_test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/kvm/x86_64/cpuid_test.c b/tools/testing/selftests/kvm/x86_64/cpuid_test.c index a6aeee2e62e4..c85113d1aeb2 100644 --- a/tools/testing/selftests/kvm/x86_64/cpuid_test.c +++ b/tools/testing/selftests/kvm/x86_64/cpuid_test.c @@ -93,7 +93,7 @@ static void compare_cpuids(const struct kvm_cpuid2 *cpuid1, TEST_ASSERT(e1->function == e2->function && e1->index == e2->index && e1->flags == e2->flags, - "CPUID entries[%d] mismtach: 0x%x.%d.%x vs. 0x%x.%d.%x\n", + "CPUID entries[%d] mismatch: 0x%x.%d.%x vs. 0x%x.%d.%x\n", i, e1->function, e1->index, e1->flags, e2->function, e2->index, e2->flags); -- 2.35.3

2 years, 5 months

1
0
0 0

Re: [PATCH net] ip_tunnel: allow to inherit from VLAN encapsulated IP frames

by Nicolas Dichtel

+ linux-kselftest(a)vger.kernel.org Le 20/07/2022 à 17:24, Matthias May a écrit : > Hi > > I finally got around to do the previously mentioned selftest for gretap, vxlan > and geneve. > See the bash-script below. > > Many of the vxlan/geneve tests are currently failing, with gretap working on > net-next > because of the fixes i sent. > What is the policy on sending selftests that are failing? > Are fixes for the failures required in advance? I don't know, I've added linux-kselftest(a)vger.kernel.org to the thread. Regards, Nicolas > > I'm not sure i can fix them. > Geneve seems to ignore the 3 upper bits of the DSCP completely.

2 years, 5 months

1
0
0 0

相互理解

by DR JOSEPH ANYA

-- 亲爱的朋友, 我是约瑟夫*安雅先生，在亚行银行在西非。我正在联系你与我合作只检索总额(3 950万美元)。押金是由我们已故的客户乔治。小。我在成功收到资金后向您提出总额的40％，我向您保证，这笔交易是100％无风险和合法的。我寻求你的合伙要求这些资金，以避免被银行没收。联系我了解更多细节。我期待你的紧急答复致以最良好的问候。约瑟夫*安雅博士。

2 years, 5 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

2017

Linux-kselftest-mirror July 2022