Can device mapper be taught to return new errors and sense codes that are part of the ZAC/ZBC spec?

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

 



Hi again;

This question is also related to the same simulator project mentioned in my previous email.

The ZAC/ZBC spec(s) specify some errors that dont currently exist. For the simulator to be successful, it needs to be able to respond appropriately to being asked to do things that other drives are allowed to do, but this one is not.

So read's and writes for the simulator have to return errors that dont currently exist in the kernel as of today.

I notice that struct dm_target has an error string entry, but that is only for the ctor and it's a string.

Can any of you provide any suggestions of guidance on this topic?

tnx!

johnu

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel




[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux