fix atomic limits check v2

[Christoph Hellwig]

On Wed, Jun 25, 2025 at 10:04:55AM -0700, alan.adamson at oracle.com wrote:
> [root at localhost ~]# nvme id-ns /dev/nvme0n2 | grep nawupf
> nawupf  : 15
> [root at localhost ~]# cat /sys/block/nvme0n2/queue/atomic_write_max_bytes
> 8192
> [root at localhost ~]# nvme id-ns /dev/nvme0n3 | grep nawupf
> nawupf  : 63
> [root at localhost ~]# cat /sys/block/nvme0n3/queue/atomic_write_max_bytes
> 32768
> [root at localhost ~]# dmesg | grep nvme | grep AWUPF
> [    2.761599] nvme nvme2: inconsistent AWUPF, controller not added (7/15).
> [    2.765669] nvme nvme1: inconsistent AWUPF, controller not added (31/15).
> [root at localhost ~]#
>
> Why was CTRL1 (nvme1) not added? AWUPF of 31 works with a 
> atomic_write_max_bytes of 8192.

Because it reports different AWUPF for controllers in the same subsystem.