[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202006242312.8888AAFE@keescook>
Date: Wed, 24 Jun 2020 23:16:03 -0700
From: Kees Cook <keescook@...omium.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Michael Ellerman <mpe@...erman.id.au>,
Joe Lawrence <joe.lawrence@...hat.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Anders Roxell <anders.roxell@...aro.org>,
Daniel Díaz <daniel.diaz@...aro.org>,
Justin Cook <justin.cook@...aro.org>,
lkft-triage@...ts.linaro.org, Miroslav Benes <mbenes@...e.cz>,
Petr Mladek <pmladek@...e.com>, Shuah Khan <shuah@...nel.org>
Subject: Re: [PATCH 1/2] selftests/lkdtm: Don't clear dmesg when running tests
On Mon, Jun 22, 2020 at 02:21:38PM +0530, Naresh Kamboju wrote:
> On Fri, 8 May 2020 at 12:23, Michael Ellerman <mpe@...erman.id.au> wrote:
> > # Record and dump the results
> > -dmesg -c >"$LOG"
> > +dmesg | diff --changed-group-format='%>' --unchanged-group-format='' "$DMESG" - > "$LOG" || true
>
> We are facing problems with the diff `=%>` part of the option.
> This report is from the OpenEmbedded environment.
> We have the same problem from livepatch_testcases.
Does "comm" exists in those environments?
dmesg | comm -13 "$DMESG" - > "$LOG" || true
this is even shorter than the diff command line. :)
--
Kees Cook
Powered by blists - more mailing lists