From: Christoph Hellwig <hch@lst.de>
To: Mark Hsieh <mark_hsieh@wistron.corp-partner.google.com>
Cc: alsa-devel@alsa-project.org, Mark_Hsieh@wistron.com,
sagi@grimberg.me, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, axboe@fb.com, kbusch@kernel.org,
hch@lst.de
Subject: Re: [PATCH] [v2] nvme-pci: disable write zeros support on specific SSDs
Date: Tue, 15 Mar 2022 14:22:02 +0100 [thread overview]
Message-ID: <20220315132202.GA12452@lst.de> (raw)
In-Reply-To: <20220315132059.12747-1-mark_hsieh@wistron.corp-partner.google.com>
On Tue, Mar 15, 2022 at 09:20:59PM +0800, Mark Hsieh wrote:
> Like commit 5611ec2b9814 ("nvme-pci: prevent SK hynix PC400 from using
> Write Zeroes command"), Micron has the same issue:
> [ 6305.633887] blk_update_request: operation not supported error, dev
> nvme0n1, sector 340812032 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0
>
> So also disable Write Zeroes command on Micron.
This still ignores all the questions I've asked.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mark Hsieh <mark_hsieh@wistron.corp-partner.google.com>
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
sagi@grimberg.me, hch@lst.de, axboe@fb.com, kbusch@kernel.org,
alsa-devel@alsa-project.org, Mark_Hsieh@wistron.com
Subject: Re: [PATCH] [v2] nvme-pci: disable write zeros support on specific SSDs
Date: Tue, 15 Mar 2022 14:22:02 +0100 [thread overview]
Message-ID: <20220315132202.GA12452@lst.de> (raw)
In-Reply-To: <20220315132059.12747-1-mark_hsieh@wistron.corp-partner.google.com>
On Tue, Mar 15, 2022 at 09:20:59PM +0800, Mark Hsieh wrote:
> Like commit 5611ec2b9814 ("nvme-pci: prevent SK hynix PC400 from using
> Write Zeroes command"), Micron has the same issue:
> [ 6305.633887] blk_update_request: operation not supported error, dev
> nvme0n1, sector 340812032 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0
>
> So also disable Write Zeroes command on Micron.
This still ignores all the questions I've asked.
next prev parent reply other threads:[~2022-03-15 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 13:20 [PATCH] [v2] nvme-pci: disable write zeros support on specific SSDs Mark Hsieh
2022-03-15 13:20 ` Mark Hsieh
2022-03-15 13:22 ` Christoph Hellwig [this message]
2022-03-15 13:22 ` Christoph Hellwig
2022-03-15 13:47 ` Sagi Grimberg
2022-03-15 13:47 ` Sagi Grimberg
[not found] ` <TY2PR02MB2752B1742028968B3DAE02EBEA129@TY2PR02MB2752.apcprd02.prod.outlook.com>
2022-03-17 17:10 ` Keith Busch
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=20220315132202.GA12452@lst.de \
--to=hch@lst.de \
--cc=Mark_Hsieh@wistron.com \
--cc=alsa-devel@alsa-project.org \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mark_hsieh@wistron.corp-partner.google.com \
--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.