Re: [PATCH blktests 0/3] tetss/nvme: fix nvme disc changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Sagi,

On 1/12/22 12:38 AM, Sagi Grimberg wrote:
External email: Use caution opening links or attachments


What is preventing this to break again?

Can we modify the tests to not rely on a consistent
output here. Perhaps just search/match the expected nvm subsystems
in the log page?

Do we expect to change the output of the log page again ?

Yes, I don't expect that we will lock down the discovery output
in both the target and nvme-cli.

It is important to match the disc subsysnqn i.e.
"nqn.2014-08.org.nvmexpress.discovery" and gencounter,
only matching the nvm subsystems not going to get us good
coverage.

I'm just saying that it is not sustainable. Nothing prevents
anyone from changing the log page again.



[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux