linux-kernel - Re: [PATCH v2 2/2] selftests: KVM: use dirty logging to check if page stats work correctly

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL715WJvYLyWS1dY_-69WEfp5HnTfCFrPNpx0OX1eOqN8D5DeA@mail.gmail.com>
Date:   Sun, 29 Aug 2021 21:42:13 -0700
From:   Mingwei Zhang <mizhang@...gle.com>
To:     kernel test robot <lkp@...el.com>
Cc:     Paolo Bonzini <pbonzini@...hat.com>, kbuild-all@...ts.01.org,
        kvm <kvm@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
        Sean Christopherson <seanjc@...gle.com>,
        David Matlack <dmatlack@...gle.com>,
        Jing Zhang <jingzhangos@...gle.com>,
        Peter Xu <peterx@...hat.com>, Ben Gardon <bgardon@...gle.com>
Subject: Re: [PATCH v2 2/2] selftests: KVM: use dirty logging to check if page
 stats work correctly

>    dirty_log_perf_test.c: In function 'run_test':
> >> dirty_log_perf_test.c:236:28: error: macro "TEST_ASSERT" requires 3 arguments, but only 1 given
>      236 |    "2M page number is zero");
>          |                            ^
>    In file included from include/kvm_util.h:10,
>                     from dirty_log_perf_test.c:17:
>    include/test_util.h:46: note: macro "TEST_ASSERT" defined here
>       46 | #define TEST_ASSERT(e, fmt, ...) \
>          |
> >> dirty_log_perf_test.c:235:3: error: 'TEST_ASSERT' undeclared (first use in this function)
>      235 |   TEST_ASSERT(get_page_stats(X86_PAGE_SIZE_2M) > 0
>          |   ^~~~~~~~~~~
>    dirty_log_perf_test.c:235:3: note: each undeclared identifier is reported only once for each function it appears in
>

Sorry, there is one fix not checked in before I sent it out. Will fix
it in the next version.