From: Kees Cook <keescook@chromium.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "Michael Ellerman" <mpe@ellerman.id.au>,
"Joe Lawrence" <joe.lawrence@redhat.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Daniel Díaz" <daniel.diaz@linaro.org>,
"Justin Cook" <justin.cook@linaro.org>,
lkft-triage@lists.linaro.org, "Miroslav Benes" <mbenes@suse.cz>,
"Petr Mladek" <pmladek@suse.com>, "Shuah Khan" <shuah@kernel.org>
Subject: Re: [PATCH 1/2] selftests/lkdtm: Don't clear dmesg when running tests
Date: Wed, 24 Jun 2020 23:16:03 -0700 [thread overview]
Message-ID: <202006242312.8888AAFE@keescook> (raw)
In-Reply-To: <CA+G9fYtHP+Gg+BrR_GkBMxu2oOi-_e9pATtpb6TVRswv1G1r1Q@mail.gmail.com>
On Mon, Jun 22, 2020 at 02:21:38PM +0530, Naresh Kamboju wrote:
> On Fri, 8 May 2020 at 12:23, Michael Ellerman <mpe@ellerman.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
next prev parent reply other threads:[~2020-06-25 6:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 6:53 [PATCH 1/2] selftests/lkdtm: Don't clear dmesg when running tests Michael Ellerman
2020-05-08 6:53 ` [PATCH 2/2] selftests/lkdtm: Use grep -E instead of egrep Michael Ellerman
2020-05-08 7:30 ` Kees Cook
2020-05-08 7:30 ` [PATCH 1/2] selftests/lkdtm: Don't clear dmesg when running tests Kees Cook
2020-06-22 8:51 ` Naresh Kamboju
2020-06-24 3:48 ` Joe Lawrence
2020-06-24 8:39 ` Petr Mladek
2020-06-24 20:12 ` Joe Lawrence
2020-06-26 8:02 ` Petr Mladek
2020-06-26 13:38 ` Joe Lawrence
2020-06-26 15:51 ` Naresh Kamboju
2020-06-25 6:16 ` Kees Cook [this message]
2020-06-26 15:50 ` Naresh Kamboju
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=202006242312.8888AAFE@keescook \
--to=keescook@chromium.org \
--cc=anders.roxell@linaro.org \
--cc=daniel.diaz@linaro.org \
--cc=joe.lawrence@redhat.com \
--cc=justin.cook@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mbenes@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=naresh.kamboju@linaro.org \
--cc=pmladek@suse.com \
--cc=shuah@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