From: Kees Cook <keescook@chromium.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, Shuah Khan <shuah@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: Wed, 26 Feb 2020 11:01:30 -0800 [thread overview]
Message-ID: <202002261052.62C3132B0@keescook> (raw)
In-Reply-To: <CA+G9fYuQJjf3v53HNj4TOAL2NcgDCYCrsUkfL6h93ntXO3WWwg@mail.gmail.com>
On Wed, Feb 26, 2020 at 11:32:46PM +0530, Naresh Kamboju wrote:
> Yeah i see this case at my end also.
>
> my two cents,
> I have two comments,
> 1) shell check
I'll fix these up; thanks for the suggestions!
> Test output with set -x for debugging shell scripts.
> [...]
> ++ dmesg -c
> +++ mktemp --tmpdir -t lkdtm-XXXXXX
> ++ LOG=/tmp/lkdtm-r5yZ7K
> ++ trap cleanup EXIT
> ++ /bin/sh -c 'cat <(echo BUG) >/sys/kernel/debug/provoke-crash/DIRECT'
> ++ true
> ++ dmesg -c
> ++ cat /tmp/lkdtm-r5yZ7K
This is the part that is failing and I don't know why.
clear the kernel event log:
dmesg -c
trigger the kernel event:
/bin/sh -c 'cat <(echo BUG) >/sys/kernel/debug/provoke-crash/DIRECT'
dump the newly added event logs into a file (set -x doesn't report
redirection to /tmp/lkdtm-r5yZ7K):
dmesg -c
It seems /tmp/lkdtm-r5yZ7K is empty?
--
Kees Cook
next prev parent reply other threads:[~2020-02-26 19:01 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
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 [this message]
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=202002261052.62C3132B0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox