public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pengfei Xu <pengfei.xu@intel.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: <nogikh@google.com>, <linux-kernel@vger.kernel.org>,
	Heng Su <heng.su@intel.com>, <syzkaller@googlegroups.com>,
	<keescook@google.com>, Mehta Sohil <sohil.mehta@intel.com>,
	<kirill.shutemov@linux.intel.com>, <akpm@linux-foundation.org>
Subject: Re: [PATCH v1 1/1] x86/kernel: Increase kcov coverage under arch/x86/kernel folder
Date: Wed, 5 Jul 2023 19:38:52 +0800	[thread overview]
Message-ID: <ZKVWTL9fMQ++oQJ0@xpf.sh.intel.com> (raw)
In-Reply-To: <CACT4Y+aBNX9U7yeH8jz5y82tV46iChCFXufg92gSXrdRubqJsw@mail.gmail.com>

Hi Dmitry,

On 2023-07-05 at 06:28:10 +0200, Dmitry Vyukov wrote:
> On Tue, 4 Jul 2023 at 10:58, Pengfei Xu <pengfei.xu@intel.com> wrote:
> >
> > Currently kcov instrument is disabled for object files under arch/x86/kernel
> > folder.
> > For object files under arch/x86/kernel, actually just disabling the kcov
> > instrument of files:"head32.o or head64.o and sev.o" could achieve
> > successful booting and provide kcov coverage for object files that do not
> > disable kcov instrument.
> > The additional kcov coverage collected from arch/x86/kernel folder helps
> > kernel fuzzing efforts to find bugs.
> >
> > Link to related improvement discussion is below:
> > https://groups.google.com/g/syzkaller/c/Dsl-RYGCqs8/m/x-tfpTyFBAAJ
> > Related ticket is as follow:
> > https://bugzilla.kernel.org/show_bug.cgi?id=198443
> >
> > Signed-off-by: Pengfei Xu <pengfei.xu@intel.com>
> 
> Reviewed-and-tested-by: Dmitry Vyukov <dvyukov@google.com>
> 
> I've run a local syzkaller instance with this and I don't see any
> additional kernel bugs caused by this and I see coverage in
> arch/x86/kernel/* now, in particular, dumpstack.c, perf_regs.c,
> signal.c.

Thanks for your tag! Yes, it can cover more code in arch/x86/kernel/.

Best Regards,
Thanks!

> 
> 
> > ---
> >  arch/x86/kernel/Makefile | 9 ++++-----
> >  1 file changed, 4 insertions(+), 5 deletions(-)
> >
> > diff --git a/arch/x86/kernel/Makefile b/arch/x86/kernel/Makefile
> > index 4070a01c11b7..00df34c263cc 100644
> > --- a/arch/x86/kernel/Makefile
> > +++ b/arch/x86/kernel/Makefile
> > @@ -33,11 +33,10 @@ KCSAN_SANITIZE := n
> >  KMSAN_SANITIZE_head$(BITS).o                           := n
> >  KMSAN_SANITIZE_nmi.o                                   := n
> >
> > -# If instrumentation of this dir is enabled, boot hangs during first second.
> > -# Probably could be more selective here, but note that files related to irqs,
> > -# boot, dumpstack/stacktrace, etc are either non-interesting or can lead to
> > -# non-deterministic coverage.
> > -KCOV_INSTRUMENT                := n
> > +# If instrumentation of the following files is enabled, boot hangs during
> > +# first second.
> > +KCOV_INSTRUMENT_head$(BITS).o                          := n
> > +KCOV_INSTRUMENT_sev.o                                  := n
> >
> >  CFLAGS_irq.o := -I $(srctree)/$(src)/../include/asm/trace
> >
> > --
> > 2.31.1
> >

      reply	other threads:[~2023-07-05 11:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1688460800.git.pengfei.xu@intel.com>
2023-07-04  9:00 ` [PATCH v1 1/1] x86/kernel: Increase kcov coverage under arch/x86/kernel folder Pengfei Xu
2023-07-05  4:28   ` Dmitry Vyukov
2023-07-05 11:38     ` Pengfei Xu [this message]

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=ZKVWTL9fMQ++oQJ0@xpf.sh.intel.com \
    --to=pengfei.xu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=heng.su@intel.com \
    --cc=keescook@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nogikh@google.com \
    --cc=sohil.mehta@intel.com \
    --cc=syzkaller@googlegroups.com \
    /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