All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2 2/3] nvme: enable to inject errors into admin commands
Date: Tue, 4 Jun 2019 09:23:36 +0200	[thread overview]
Message-ID: <20190604072336.GC15680@lst.de> (raw)
In-Reply-To: <1559483421-11361-3-git-send-email-akinobu.mita@gmail.com>

>  	struct nvme_fault_inject *fault_inject = NULL;
>  	u16 status;
>  
> -	/*
> -	 * make sure this request is coming from a valid namespace
> -	 */
>  	if (disk) {
>  		struct nvme_ns *ns = disk->private_data;
>  
>  		if (ns)
>  			fault_inject = &ns->fault_inject;


Not new in this code, but how could ns ever be NULL here?

> @@ -257,6 +266,8 @@ struct nvme_ctrl {
>  	 */
>  	struct thermal_zone_device *tzdev[9];
>  #endif

Looks like this series seem to be based on the thermal zone series.

> -struct nvme_fault_inject {
> -#ifdef CONFIG_FAULT_INJECTION_DEBUG_FS
> -	struct fault_attr attr;
> -	struct dentry *parent;
> -	bool dont_retry;	/* DNR, do not retry */
> -	u16 status;		/* status code */
> -#endif

It would be nicer to already move it up earlier when you change the ifdef
guared.

Otherwise the whole series looks fine:

Reviewed-by: Christoph Hellwig <hch at lst.de>

  parent reply	other threads:[~2019-06-04  7:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-02 13:50 [PATCH v2 0/3] nvme: enable to inject errors into admin commands Akinobu Mita
2019-06-02 13:50 ` [PATCH v2 1/3] nvme: prepare for fault injection " Akinobu Mita
2019-06-02 22:49   ` Chaitanya Kulkarni
2019-06-02 13:50 ` [PATCH v2 2/3] nvme: enable to inject errors " Akinobu Mita
2019-06-02 22:49   ` Chaitanya Kulkarni
2019-06-04  7:23   ` Christoph Hellwig [this message]
2019-06-04 13:36     ` Akinobu Mita
2019-06-02 13:50 ` [PATCH v2 3/3] Documentation: nvme: add an example for nvme fault injection Akinobu Mita
2019-06-02 22:49   ` Chaitanya Kulkarni
     [not found] ` <CGME20190602135117epcas4p14feefbe2556a469008a7a499174e5b43@epcms2p1>
2019-06-03  4:37   ` Minwoo Im

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=20190604072336.GC15680@lst.de \
    --to=hch@lst.de \
    /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.