All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Alan Adamson <alan.adamson@oracle.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
	osandov@fb.com
Subject: Re: blktests v4 tests/nvme: add tests for error logging
Date: Tue, 17 May 2022 16:47:31 -0700	[thread overview]
Message-ID: <YoQ0E8s6gFczuppP@relinquished.localdomain> (raw)
In-Reply-To: <20220516225539.81588-1-alan.adamson@oracle.com>

On Mon, May 16, 2022 at 03:55:37PM -0700, Alan Adamson wrote:
> Test nvme error logging by injecting errors. Kernel must have FAULT_INJECTION
> and FAULT_INJECTION_DEBUG_FS configured to use error injector. Tests can be
> run with or without NVME_VERBOSE_ERRORS configured.
> 
> These test verify the functionality delivered by the follow:
>         commit bd83fe6f2cd2 ("nvme: add verbose error logging")
> 
> V2 - Update from suggestions from shinichiro.kawasaki@wdc.com
> V3 - Add error injector helper functions to nvme/rc
> V4 - Comments from shinichiro.kawasaki@wdc.com 
> 
> Alan Adamson (2):
>   tests/nvme: add helper routine to use error injector
>   tests/nvme: add tests for error logging
> 
>  tests/nvme/039     | 153 +++++++++++++++++++++++++++++++++++++++++++++
>  tests/nvme/039.out |   7 +++
>  tests/nvme/rc      |  44 +++++++++++++
>  3 files changed, 204 insertions(+)
>  create mode 100755 tests/nvme/039
>  create mode 100644 tests/nvme/039.out

Thanks, applied.

      parent reply	other threads:[~2022-05-17 23:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 22:55 blktests v4 tests/nvme: add tests for error logging Alan Adamson
2022-05-16 22:55 ` [PATCH v4 blktests 1/2] tests/nvme: add helper routine to use error injector Alan Adamson
2022-05-16 22:55 ` [PATCH v4 blktests 2/2] tests/nvme: add tests for error logging Alan Adamson
2022-05-17  6:23 ` blktests v4 " Shinichiro Kawasaki
2022-05-17 22:58   ` Chaitanya Kulkarni
2022-05-17 23:47 ` Omar Sandoval [this message]

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=YoQ0E8s6gFczuppP@relinquished.localdomain \
    --to=osandov@osandov.com \
    --cc=alan.adamson@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=osandov@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.