[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <202002261052.62C3132B0@keescook>
Date: Wed, 26 Feb 2020 11:01:30 -0800
From: Kees Cook <keescook@...omium.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Cristian Marussi <cristian.marussi@....com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>, Shuah Khan <shuah@...nel.org>,
Anders Roxell <anders.roxell@...aro.org>,
lkft-triage@...ts.linaro.org,
open list <linux-kernel@...r.kernel.org>, ankita@...ibm.com,
Will Deacon <will@...nel.org>, ardb@...nel.org,
"Guohanjun (Hanjun Guo)" <guohanjun@...wei.com>
Subject: Re: selftests: Linux Kernel Dump Test Module output
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
Powered by blists - more mailing lists