All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: shuah <shuah@kernel.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	Anders Roxell <anders.roxell@linaro.org>,
	lkft-triage@lists.linaro.org,
	open list <linux-kernel@vger.kernel.org>,
	ankita@in.ibm.com, Will Deacon <will@kernel.org>,
	ardb@kernel.org, "Guohanjun (Hanjun Guo)" <guohanjun@huawei.com>
Subject: Re: selftests: Linux Kernel Dump Test Module output
Date: Thu, 20 Feb 2020 16:16:01 -0800	[thread overview]
Message-ID: <202002201610.2B149A6D@keescook> (raw)
In-Reply-To: <31b066c2-d1c9-1592-48cd-bccb4b3a624a@kernel.org>

On Wed, Feb 19, 2020 at 09:16:03AM -0700, shuah wrote:
> On 2/17/20 8:36 AM, Cristian Marussi wrote:
> > Hi
> > 
> > n 17/02/2020 11:09, Naresh Kamboju wrote:
> > > The selftest lkdtm test failed on x86_64 and arm64.
> > > am I missing any pre-requisite?
> > > 
> > > Boot log:
> > > [    3.297812] lkdtm: No crash points registered, enable through debugfs
> > > 
> > 
> > from your logs I cannot deduce anything useful, but in our CI I've got similar issues
> > since the 10/12th of Feb...
> > 
> > TAP version 13
> > 1..71
> > # selftests: lkdtm: PANIC.sh
> > # Cannot find /sys/kernel/debug/provoke-crash/DIRECT (missing CONFIG_LKDTM?)
> > not ok 1 selftests: lkdtm: PANIC.sh # SKIP
> > # selftests: lkdtm: BUG.sh
> > # Cannot find /sys/kernel/debug/provoke-crash/DIRECT (missing CONFIG_LKDTM?)
> > 
> > so I suppose this and a bunch of other (probably new) tests are simply
> > missing a bit of CONFIGs... (but I have still to look into this properly)
> > (not sure if this also is your case either...)
> > 
> > Regards
> > 
> > Cristian
> > 
> 
> Hi Kees,
> 
> Any ideas on what this is about? Missing config or something else?

In the first case, I'm not sure what's happening -- the logs don't seem
to show anything, but the lkdtm should be available (from the boot log).

In the second case, yes, it looks like missing CONFIG_LKDTM (the test
even has a "config" file). Either CONFIG_LKDTM=y or CONFIG_LKDTM=m will
work (the test running will attempt to load the lkdtm module if it's
missing).

A final option is that either the debug filesystem isn't mounted, or is
mounted somewhere "non-standard"? (I'd expect a lot of things to fail...)

-Kees

-- 
Kees Cook

  reply	other threads:[~2020-02-21  0:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 11:09 selftests: Linux Kernel Dump Test Module output Naresh Kamboju
2020-02-17 15:36 ` Cristian Marussi
2020-02-19 16:16   ` shuah
2020-02-21  0:16     ` Kees Cook [this message]
2020-02-25 19:31   ` Kees Cook
2020-02-26 11:53     ` Cristian Marussi
2020-02-26 18:02       ` Naresh Kamboju
2020-02-26 19:01         ` Kees Cook
2020-02-26 18:49       ` Kees Cook
2020-02-25 19:31 ` Kees Cook

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=202002201610.2B149A6D@keescook \
    --to=keescook@chromium.org \
    --cc=anders.roxell@linaro.org \
    --cc=ankita@in.ibm.com \
    --cc=ardb@kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=shuah@kernel.org \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.