From: Greg KH <greg@kroah.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: stable@vger.kernel.org, David Milburn <dmilburn@redhat.com>,
Eric Sandeen <esandeen@redhat.com>,
Eric Sandeen <sandeen@redhat.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] nvme-pci: disable the write zeros command for Intel 600P/P3100
Date: Wed, 21 Oct 2020 14:14:46 +0200 [thread overview]
Message-ID: <20201021121446.GB1150778@kroah.com> (raw)
In-Reply-To: <20201021120415.19722-1-jandryuk@gmail.com>
On Wed, Oct 21, 2020 at 08:04:15AM -0400, Jason Andryuk wrote:
> From: David Milburn <dmilburn@redhat.com>
>
> [ Upstream commit ce4cc3133dc72c31bd49ddcf22d0f9eeff47a761 ]
>
> The write zeros command does not work with 4k range.
>
> bash-4.4# ./blkdiscard /dev/nvme0n1p2
> bash-4.4# strace -efallocate xfs_io -c "fzero 536895488 2048" /dev/nvme0n1p2
> fallocate(3, FALLOC_FL_ZERO_RANGE, 536895488, 2048) = 0
> +++ exited with 0 +++
> bash-4.4# dd bs=1 if=/dev/nvme0n1p2 skip=536895488 count=512 | hexdump -C
> 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> *
> 00000200
>
> bash-4.4# ./blkdiscard /dev/nvme0n1p2
> bash-4.4# strace -efallocate xfs_io -c "fzero 536895488 4096" /dev/nvme0n1p2
> fallocate(3, FALLOC_FL_ZERO_RANGE, 536895488, 4096) = 0
> +++ exited with 0 +++
> bash-4.4# dd bs=1 if=/dev/nvme0n1p2 skip=536895488 count=512 | hexdump -C
> 00000000 5c 61 5c b0 96 21 1b 5e 85 0c 07 32 9c 8c eb 3c |\a\..!.^...2...<|
> 00000010 4a a2 06 ca 67 15 2d 8e 29 8d a8 a0 7e 46 8c 62 |J...g.-.)...~F.b|
> 00000020 bb 4c 6c c1 6b f5 ae a5 e4 a9 bc 93 4f 60 ff 7a |.Ll.k.......O`.z|
>
> Reported-by: Eric Sandeen <esandeen@redhat.com>
> Signed-off-by: David Milburn <dmilburn@redhat.com>
> Tested-by: Eric Sandeen <sandeen@redhat.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> [ Fix-up for 5.4 since NVME_QUIRK_NO_TEMP_THRESH_CHANGE doesn't exist ]
> Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
>
> ---
> Applicable to 5.4. NVME_QUIRK_DISABLE_WRITE_ZEROES was introduced in 5.0.
> The original commit needs a fix for 5.4 because
> NVME_QUIRK_NO_TEMP_THRESH_CHANGE doesn't exist - it looks like it was
> added in 5.5.
>
> Observed with mke2fs failures on 5.4 wih Intel 600P.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2020-10-21 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 12:04 [PATCH] nvme-pci: disable the write zeros command for Intel 600P/P3100 Jason Andryuk
2020-10-21 12:14 ` Greg KH [this message]
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=20201021121446.GB1150778@kroah.com \
--to=greg@kroah.com \
--cc=dmilburn@redhat.com \
--cc=esandeen@redhat.com \
--cc=hch@lst.de \
--cc=jandryuk@gmail.com \
--cc=sandeen@redhat.com \
--cc=stable@vger.kernel.org \
/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.