From: Peter Zijlstra <peterz@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org, syzkaller@googlegroups.com,
elver@google.com, glider@google.com, nogikh@google.com,
tarasmadan@google.com
Subject: Re: [PATCH v2 2/4] kcov: add interrupt handling self test
Date: Wed, 19 Jun 2024 13:13:09 +0200 [thread overview]
Message-ID: <20240619111309.GJ31592@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <7662127c97e29da1a748ad1c1539dd7b65b737b2.1718092070.git.dvyukov@google.com>
On Tue, Jun 11, 2024 at 09:50:31AM +0200, Dmitry Vyukov wrote:
> Add a boot self test that can catch sprious coverage from interrupts.
> The coverage callback filters out interrupt code, but only after the
> handler updates preempt count. Some code periodically leaks out
> of that section and leads to spurious coverage.
> Add a best-effort (but simple) test that is likely to catch such bugs.
> If the test is enabled on CI systems that use KCOV, they should catch
> any issues fast.
>
> Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
> Reviewed-by: Alexander Potapenko <glider@google.com>
> Cc: x86@kernel.org
> Cc: linux-kernel@vger.kernel.org
> Cc: syzkaller@googlegroups.com
>
> ---
>
> Changed since v1:
> - renamed KCOV_TEST to KCOV_SELFTEST
> - improved the config description
> - loop for exactly 300ms in the test
>
> In my local testing w/o the previous fix,
> it immidiatly produced the following splat:
>
> kcov: running selftest
> BUG: TASK stack guard page was hit at ffffc90000147ff8
> Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN PTI
> ...
> kvm_set_cpu_l1tf_flush_l1d+0x5/0x20
> sysvec_call_function+0x15/0xb0
> asm_sysvec_call_function+0x1a/0x20
> kcov_init+0xe4/0x130
> do_one_initcall+0xbc/0x470
> kernel_init_freeable+0x4fc/0x930
> kernel_init+0x1c/0x2b0
So I'm not entirely sure how the above BUG comes about, nor how this
selftest tickles it. Could you elaborate?
I've found check_kcov_mode() which has this !in_task() clause, but I'm
not entirely sure how failing that leads to the above mentioned failure.
> ---
> kernel/kcov.c | 31 +++++++++++++++++++++++++++++++
> lib/Kconfig.debug | 8 ++++++++
> 2 files changed, 39 insertions(+)
>
> diff --git a/kernel/kcov.c b/kernel/kcov.c
> index c3124f6d5536..72a5bf55107f 100644
> --- a/kernel/kcov.c
> +++ b/kernel/kcov.c
> @@ -11,6 +11,7 @@
> #include <linux/fs.h>
> #include <linux/hashtable.h>
> #include <linux/init.h>
> +#include <linux/jiffies.h>
> #include <linux/kmsan-checks.h>
> #include <linux/mm.h>
> #include <linux/preempt.h>
> @@ -1057,6 +1058,32 @@ u64 kcov_common_handle(void)
> }
> EXPORT_SYMBOL(kcov_common_handle);
>
> +#ifdef CONFIG_KCOV_SELFTEST
> +static void __init selftest(void)
> +{
> + unsigned long start;
> +
> + pr_err("running self test\n");
> + /*
> + * Test that interrupts don't produce spurious coverage.
> + * The coverage callback filters out interrupt code, but only
> + * after the handler updates preempt count. Some code periodically
> + * leaks out of that section and leads to spurious coverage.
> + * It's hard to call the actual interrupt handler directly,
> + * so we just loop here for a bit waiting for a timer interrupt.
> + * We set kcov_mode to enable tracing, but don't setup the area,
> + * so any attempt to trace will crash. Note: we must not call any
> + * potentially traced functions in this region.
> + */
> + start = jiffies;
> + current->kcov_mode = KCOV_MODE_TRACE_PC;
barrier();
> + while ((jiffies - start) * MSEC_PER_SEC / HZ < 300)
> + ;
barrier();
> + current->kcov_mode = 0;
> + pr_err("done running self test\n");
> +}
> +#endif
next prev parent reply other threads:[~2024-06-19 11:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 7:50 [PATCH v2 0/4] KCOV fixes Dmitry Vyukov
2024-06-11 7:50 ` [PATCH v2 1/4] x86/entry: Remove unwanted instrumentation in common_interrupt() Dmitry Vyukov
2024-06-19 11:19 ` Peter Zijlstra
2024-06-19 13:05 ` Dmitry Vyukov
2024-08-08 15:49 ` [tip: x86/build] " tip-bot2 for Dmitry Vyukov
2024-06-11 7:50 ` [PATCH v2 2/4] kcov: add interrupt handling self test Dmitry Vyukov
2024-06-11 9:29 ` Marco Elver
2024-06-13 23:01 ` Andrey Konovalov
2024-06-19 11:13 ` Peter Zijlstra [this message]
2024-06-19 11:18 ` Dmitry Vyukov
2024-06-19 11:26 ` Peter Zijlstra
2024-08-08 15:49 ` [tip: x86/build] kcov: Add " tip-bot2 for Dmitry Vyukov
2024-06-11 7:50 ` [PATCH v2 3/4] module: Fix KCOV-ignored file name Dmitry Vyukov
2024-06-11 9:29 ` Marco Elver
2024-06-13 22:55 ` Andrey Konovalov
2024-08-08 15:49 ` [tip: x86/build] " tip-bot2 for Dmitry Vyukov
2024-06-11 7:50 ` [PATCH v2 4/4] x86: Ignore stack unwinding in KCOV Dmitry Vyukov
2024-06-13 22:51 ` Andrey Konovalov
2024-06-19 11:23 ` Peter Zijlstra
2024-06-19 13:10 ` Dmitry Vyukov
2024-08-08 15:49 ` [tip: x86/build] " tip-bot2 for Dmitry Vyukov
2024-06-11 9:31 ` [PATCH v2 0/4] KCOV fixes Dmitry Vyukov
2024-06-19 5:20 ` Dmitry Vyukov
2024-06-19 8:30 ` Borislav Petkov
2024-08-05 12:52 ` Andrey Konovalov
2024-08-08 15:18 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240619111309.GJ31592@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nogikh@google.com \
--cc=syzkaller@googlegroups.com \
--cc=tarasmadan@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®