linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Salyzyn <salyzyn@android.com>
To: Hiraku Toyooka <hiraku.toyooka.gu@hitachi.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 <seiji.aguchi.tr@hitachi.com>
Subject: Re: [PATCH v2 2/2] selftests/pstore: add pstore test scripts going with reboot
Date: Fri, 2 Oct 2015 12:39:39 -0700	[thread overview]
Message-ID: <560EDD7B.1000406@android.com> (raw)
In-Reply-To: <20151002114641.20957.60082.stgit@arietta>

On 10/02/2015 04:46 AM, Hiraku Toyooka wrote:
> To test pstore in earnest, we have to cause kernel crash and check
> pstore filesystem after reboot.
>
> We add two scripts:
>   - pstore_crash_test
>       This script causes kernel crash and reboot. It is executed by
>       'make run_pstore_crash' in selftests. It can also be used with kdump.
>   - pstore_post_reboot_tests
>       This script includes test cases which check pstore's behavior after
>       crash and reboot. It is executed together with pstore_tests by
>       'make run_tests [-C pstore]' in selftests.
>
+1

  reply	other threads:[~2015-10-02 19:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 11:46 [PATCH v2 0/2] selftests/pstore: add pstore test script Hiraku Toyooka
2015-10-02 11:46 ` [PATCH v2 1/2] selftests/pstore: add pstore test script for pre-reboot Hiraku Toyooka
2015-10-02 19:39   ` Mark Salyzyn
2015-10-02 11:46 ` [PATCH v2 2/2] selftests/pstore: add pstore test scripts going with reboot Hiraku Toyooka
2015-10-02 19:39   ` Mark Salyzyn [this message]
2015-10-06 17:59 ` [PATCH v2 0/2] selftests/pstore: add pstore test script Shuah Khan

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=560EDD7B.1000406@android.com \
    --to=salyzyn@android.com \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=hiraku.toyooka.gu@hitachi.com \
    --cc=keescook@chromium.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).