All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: "Anner, Ran" <Ran.Anner@dell.com>,
	"Grupi, Elad" <Elad.Grupi@dell.com>,
	Frederick.Knight@netapp.com,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"Engel, Amit" <Amit.Engel@dell.com>
Subject: Re: fabrics connect cmd with a non-zero reserved value
Date: Thu, 14 Jan 2021 17:35:46 +0000	[thread overview]
Message-ID: <20210114173546.GA1872345@infradead.org> (raw)
In-Reply-To: <69465d48-5a63-5c49-50aa-39c4f921ed4a@grimberg.me>

On Wed, Jan 13, 2021 at 05:10:05PM -0800, Sagi Grimberg wrote:
> OK, now I see the issue.
> 
> This appears to me this would be an issue with the spec. As the connect
> data (like any command payload) is coming in the form of an sgl.

Reserved fields in host to controller data structure may be checked,
but may also not.  So we can verify anyting we think is to bogus to
pass, but there is not requirement for the controller to check every
reserved field or bit.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-01-14 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 10:37 fabrics connect cmd with a non-zero reserved value Engel, Amit
2021-01-14  0:34 ` Sagi Grimberg
2021-01-14  1:10   ` Sagi Grimberg
2021-01-14 17:35     ` Christoph Hellwig [this message]
2021-01-14 17:45       ` Engel, Amit
2021-01-14 21:12         ` Sagi Grimberg

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=20210114173546.GA1872345@infradead.org \
    --to=hch@infradead.org \
    --cc=Amit.Engel@dell.com \
    --cc=Elad.Grupi@dell.com \
    --cc=Frederick.Knight@netapp.com \
    --cc=Ran.Anner@dell.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.