diff options
| author | Christoph Hellwig <hch@lst.de> | 2024-11-27 09:42:18 +0300 |
|---|---|---|
| committer | Keith Busch <kbusch@kernel.org> | 2024-12-02 21:03:19 +0300 |
| commit | 58a0c875ce028678c9594c7bdf3fe33462392808 (patch) | |
| tree | 89dbd52eaddbdf3f1d3db40eb6927ec4c0ad0718 /tools/perf/scripts/python/task-analyzer.py | |
| parent | 84909f7decbd8981a24be829f110c248ecb8c51a (diff) | |
| download | linux-58a0c875ce028678c9594c7bdf3fe33462392808.tar.xz | |
nvme: don't apply NVME_QUIRK_DEALLOCATE_ZEROES when DSM is not supported
Commit 63dfa1004322 ("nvme: move NVME_QUIRK_DEALLOCATE_ZEROES out of
nvme_config_discard") started applying the NVME_QUIRK_DEALLOCATE_ZEROES
quirk even then the Dataset Management is not supported. It turns out
that there versions of these old Intel SSDs that have DSM support
disabled in the firmware, which will now lead to errors everytime
a Write Zeroes command is issued. Fix this by checking for DSM support
before applying the quirk.
Reported-by: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
Fixes: 63dfa1004322 ("nvme: move NVME_QUIRK_DEALLOCATE_ZEROES out of nvme_config_discard")
Tested-by: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Nitesh Shetty <nj.shetty@samsung.com>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions