From: Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>
To: Mark Salyzyn <salyzyn@android.com>, <linux-kernel@vger.kernel.org>
Cc: Tony Luck <tony.luck@intel.com>,
Kees Cook <keescook@chromium.org>, <linux-api@vger.kernel.org>,
Anton Vorontsov <anton@enomsg.org>,
Shuah Khan <shuahkh@osg.samsung.com>,
Colin Cross <ccross@android.com>, <seiji.aguchi.tr@hitachi.com>
Subject: Re: [PATCH 1/2] selftests/pstore: add pstore test script for pre-reboot
Date: Tue, 15 Sep 2015 11:30:40 +0900 [thread overview]
Message-ID: <55F782D0.6000501@hitachi.com> (raw)
In-Reply-To: <55EF6DC5.2080207@android.com>
Hello Mark,
Thank you for your advise.
>> +prlog -n "Checking pmsg file contains TEST_STRING ... "
> Mark this as 'wish to have'
OK. I'll change it to "Checking pmsg file wishes to have TEST_STRING
... ". Should I change other messages in the same way?
> Can TEST_STRING be given an unique value each run, so that on the the
> reboot-comparison run it can be found to be an unique match?
Yes. I'll append /proc/sys/kernel/random/uuid content to TEST_STRING.
I'll also change log directory name from date to the uuid.
> Also confirm that any previous content (which may be binary) is not
> present after reboot, and that totally new content is present.
OK.
As for pmsg, they are possible by checking if the /sys/fs/pstore/pmsg
content perfectly matches the TEST_STRING which was written to /dev/pmsg
before reboot. (The TEST_STRING can be left to a regular file before
reboot as well as reboot_flag.) Is it OK?
Best regards,
Hiraku Toyooka
--
Hiraku Toyooka
Systems Productivity Research Dept. / Linux Technology Center
Center for Technology Innovation - Systems Engineering, Hitachi Ltd.
next prev parent reply other threads:[~2015-09-15 2:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 11:06 [PATCH 0/2] selftests/pstore: add pstore test script Hiraku Toyooka
2015-09-08 11:06 ` [PATCH 1/2] selftests/pstore: add pstore test script for pre-reboot Hiraku Toyooka
2015-09-08 23:22 ` Mark Salyzyn
2015-09-15 2:30 ` Hiraku Toyooka [this message]
2015-09-21 21:04 ` Mark Salyzyn
2015-09-29 7:18 ` Hiraku Toyooka
2015-09-08 23:37 ` Kees Cook
2015-09-15 2:31 ` Hiraku Toyooka
2015-09-16 12:02 ` 阿口誠司 / AGUCHI,SEIJI
2015-09-17 5:54 ` Hiraku Toyooka
2015-09-08 11:06 ` [PATCH 2/2] selftests/pstore: add pstore test scripts going with reboot Hiraku Toyooka
2015-09-08 23:40 ` Kees Cook
2015-09-15 2:41 ` Hiraku Toyooka
2015-09-16 12:11 ` 阿口誠司 / AGUCHI,SEIJI
2015-09-17 5:54 ` Hiraku Toyooka
2015-09-08 23:42 ` [PATCH 0/2] selftests/pstore: add pstore test script 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=55F782D0.6000501@hitachi.com \
--to=hiraku.toyooka.gu@hitachi.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=salyzyn@android.com \
--cc=seiji.aguchi.tr@hitachi.com \
--cc=shuahkh@osg.samsung.com \
--cc=tony.luck@intel.com \
/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
Powered by JetHome