From: ednadols@linux.microsoft.com (Edmund Nadolski)
Subject: [PATCH] nvme: Fix known effects
Date: Fri, 17 May 2019 10:28:37 -0700 [thread overview]
Message-ID: <793cd908-fa0d-74e6-0a0a-eba0e28bcdb5@linux.microsoft.com> (raw)
In-Reply-To: <20190517161346.25102-1-keith.busch@intel.com>
On 5/17/19 9:13 AM, Keith Busch wrote:
> We're trying to append known effects to the ones reported in the
> controller's log. The original patch accomplished this, but something
> went wrong when patch was merged causing the effects log to override
> the known effects.
>
> Link: http://lists.infradead.org/pipermail/linux-nvme/2019-May/023710.html
> Cc: Maxim Levitsky <mlevitsk at redhat.com>
> Signed-off-by: Keith Busch <keith.busch at intel.com>
> ---
> drivers/nvme/host/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index f2411d50e764..5175451916d1 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -1273,9 +1273,9 @@ static u32 nvme_passthru_start(struct nvme_ctrl *ctrl, struct nvme_ns *ns,
> return 0;
> }
>
> - effects |= nvme_known_admin_effects(opcode);
> if (ctrl->effects)
> effects = le32_to_cpu(ctrl->effects->acs[opcode]);
> + effects |= nvme_known_admin_effects(opcode);
>
> /*
> * For simplicity, IO to all namespaces is quiesced even if the command
>
LGTM
Ed
next prev parent reply other threads:[~2019-05-17 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190517161939epcas5p2993c25cc84f606cfa595cecd73698c25@epcms2p3>
2019-05-17 16:13 ` [PATCH] nvme: Fix known effects Keith Busch
2019-05-17 17:28 ` Edmund Nadolski [this message]
2019-05-17 17:32 ` Chaitanya Kulkarni
2019-05-21 6:49 ` Christoph Hellwig
2019-05-21 7:26 ` 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=793cd908-fa0d-74e6-0a0a-eba0e28bcdb5@linux.microsoft.com \
--to=ednadols@linux.microsoft.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