From: Orlando Chamberlain <redecorating@protonmail.com>
To: Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org, sagi@grimberg.me, hch@lst.de
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk,
Sven Peter <sven@svenpeter.dev>,
Aditya Garg <gargaditya08@live.com>
Subject: Re: [PATCHv2] nvme: add command id quirk for apple controllers
Date: Tue, 28 Sep 2021 03:55:48 +0000 [thread overview]
Message-ID: <38101793-e0b9-ecf4-d235-465cb8e334b3@protonmail.com> (raw)
In-Reply-To: <20210927154306.387437-1-kbusch@kernel.org>
On 28/9/21 01:43, Keith Busch wrote:
> Some apple controllers use the command id as an index to implementation
> specific data structures and will fail if the value is out of bounds.
> The nvme driver's recently introduced command sequence number breaks
> this controller.
>
> Provide a quirk so these spec incompliant controllers can function as
> before. The driver will not have the ability to detect bad completions
> when this quirk is used, but we weren't previously checking this anyway.
>
> The quirk bit was selected so that it can readily apply to stable.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=214509
> Cc: Sven Peter <sven@svenpeter.dev>
> Reported-by: Orlando Chamberlain <redecorating@protonmail.com>
> Reported-by: Aditya Garg <gargaditya08@live.com>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
> v1->v2: fixed logical bug checking the quirk setting
>
> drivers/nvme/host/core.c | 4 +++-
> drivers/nvme/host/nvme.h | 6 ++++++
> drivers/nvme/host/pci.c | 3 ++-
> 3 files changed, 11 insertions(+), 2 deletions(-)
Works on my MacBookPro16,1.
Tested-by: Orlando Chamberlain <redecorating@protonmail.com>
next prev parent reply other threads:[~2021-09-28 3:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 15:43 Keith Busch
2021-09-27 15:48 ` Christoph Hellwig
2021-09-27 16:01 ` Jens Axboe
2021-09-27 15:59 ` Sven Peter
2021-09-28 3:55 ` Orlando Chamberlain [this message]
2021-09-28 5:38 ` Aditya Garg
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=38101793-e0b9-ecf4-d235-465cb8e334b3@protonmail.com \
--to=redecorating@protonmail.com \
--cc=axboe@kernel.dk \
--cc=gargaditya08@live.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sven@svenpeter.dev \
/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
all inboxes | Powered by JetHome®