What were you trying to do that didn't work?

Please provide the package NVR for which bug is seen:

Issue exits in RHEL 9.3, 9.2  and 9.1  (5.14.0-162.6.1.el9_1.x86_64) also.

Steps to reproduce

[root@localhost ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 9.3 (Plow)

[root@localhost ~]# uname -r

5.14.0-362.24.1.el9_3.x86_64

[root@localhost ~]# nvme telemetry-log /dev/nvme0 -d 1 --output-file=telemetry_testing-log_d1.bin

[root@localhost ~]# nvme telemetry-log /dev/nvme0 -d 2 --output-file=telemetry_testing-log_d2.bin

[root@localhost ~]# nvme telemetry-log /dev/nvme0 -d 3 --output-file=telemetry_testing-log_d3.bin

[root@localhost ~]# ls -lrt
rw-rr-.  1 root root      512 Mar 26 15:25 telemetry_testing-log_d1.bin
rw-rr-.  1 root root      512 Mar 26 15:25 telemetry_testing-log_d2.bin
rw-rr-.  1 root root      512 Mar 26 15:25 telemetry_testing-log_d3.bin

Expected results

Nvme telemetry logs with the different data area set should collect the logs with the different size as expected in RHEL 9.0, Below is the results from RHEL 9.

[root@localhost ~]# uname -r
5.14.0-70.13.1.el9_0.x86_64

[root@localhost ~]# nvme telemetry-log /dev/nvme1n1 --output-file=default.bin
[root@localhost ~]# nvme telemetry-log /dev/nvme1n1 -d 1 --output-file=default1.bin
[root@localhost ~]# nvme telemetry-log /dev/nvme1n1 -d 2 --output-file=default2.bin
[root@localhost ~]# nvme telemetry-log /dev/nvme1n1 -d 3 --output-file=default3.bin
[root@localhost ~]# ls -l
total 18668
rw------. 1 root root    1086 Mar 25 18:30 anaconda-ks.cfg
rw-rr-. 1 root root   86528 Mar 25 19:48 default1.bin
rw-rr-. 1 root root 2045440 Mar 25 19:48 default2.bin
rw-rr-. 1 root root 8483840 Mar 25 19:48 default3.bin
rw-rr-. 1 root root 8483840 Mar 25 19:48 default.bin
                       

Actual results:

Nvme telemetry-log for different data area 1,2 & 3 collecting the same size of the logs and observed it generates only 512 bytes of logs.