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: <CACT4Y+Zq3t2JXEbGDzYU61Rs5KH3mhCDiZ4GP9OacKuyocnYHQ@mail.gmail.com>
Date: Wed, 19 Jun 2024 07:20:56 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, 
	dave.hansen@...ux.intel.com, x86@...nel.org
Cc: linux-kernel@...r.kernel.org, syzkaller@...glegroups.com, elver@...gle.com, 
	glider@...gle.com, nogikh@...gle.com, tarasmadan@...gle.com
Subject: Re: [PATCH v2 0/4] KCOV fixes

On Tue, 11 Jun 2024 at 11:31, Dmitry Vyukov <dvyukov@...gle.com> wrote:
> > Fix spurious KCOV coverage from interrupts and add a test.
> > Ignore some additional files that lead to large amounts
> > of uninteresting coverage.
> > As a reference point, tracing a simple open system call
> > produces ~10K PCs with these changes instead of ~45K PCs.
> >
> > Dmitry Vyukov (4):
> >   x86/entry: Remove unwanted instrumentation in common_interrupt()
> >   kcov: add interrupt handling self test
> >   module: Fix KCOV-ignored file name
> >   x86: Ignore stack unwinding in KCOV
> >
> >  arch/x86/include/asm/hardirq.h  |  8 ++++++--
> >  arch/x86/include/asm/idtentry.h |  6 +++---
> >  arch/x86/kernel/Makefile        |  8 ++++++++
> >  kernel/kcov.c                   | 31 +++++++++++++++++++++++++++++++
> >  kernel/module/Makefile          |  2 +-
> >  lib/Kconfig.debug               |  8 ++++++++
> >  6 files changed, 57 insertions(+), 6 deletions(-)
> >
> >
> > base-commit: 83a7eefedc9b56fe7bfeff13b6c7356688ffa670
> > --
> > 2.45.2.505.gda0bf45e8d-goog
>
> Thomas, Ingo, Borislav, Dave,
>
> Can you take this via x86 tree please?

Or is it OK to take this via mm tree (where KCOV changes usually go)?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ