summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorKarl Bonde Torp <k.torp@samsung.com>2026-09-29 16:25:00 +0200
committerKeith Busch <kbusch@kernel.org>2026-10-03 01:55:22 -0700
commit564e46d9f6e87912effa03f123d37a511d520f09 (patch)
tree4f47b041cf1fa9128d2c8c02ff1835e29a6bfdb1 /tools/perf/scripts/python/stackcollapse.py
parentd99bc5b456fd63be46c8bda20dbf6ede93d2fc11 (diff)
downloadlinux-next-564e46d9f6e87912effa03f123d37a511d520f09.tar.gz
linux-next-564e46d9f6e87912effa03f123d37a511d520f09.zip
nvme: fix swapped ZRASF zone state values for full and read only
The Zone Management Receive command Zone Receive Action Specific (ZRASF) reporting option values for the Full and Read Only zone states are swapped compared to the NVM Express Zoned Namespace Command Set Specification, Revision 1.5, Figure 35: - 5h lists the zones in the ZSF:Full state. - 6h lists the zones in the ZSRO:Read Only state. The nvmet ZNS backend uses these constants to map the ZRASF value received from the host to a block layer zone condition when filtering zones in Report Zones. Because of the swap, a host asking for full zones was given the read only zones, and a host asking for read only zones was given the full zones. Swap the values of NVME_ZRASF_ZONE_STATE_FULL and NVME_ZRASF_ZONE_STATE_READONLY to match the specification. Fixes: aaf2e048af27 ("nvmet: add ZBD over ZNS backend support") Cc: stable@vger.kernel.org Reviewed-by: Damien Le Moal <dlemoal@kernel.org> Signed-off-by: Karl Bonde Torp <k.torp@samsung.com> Signed-off-by: Andreas Hindborg <a.hindborg@kernel.org> Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions