On 3/29/19 3:52 AM, Richard W.M. Jones wrote:
The full and null plugins should probably have a trivial .extents that reports completely sparse, all of the time :)
I think it would be wrong for full wouldn't it? It could mean that the client would skip the read, thus not getting the intended ENOSPC error. For null I agree.
The full plugin always reads as 0 successfully. It is only writes that differ (successfully ignored vs ENOSPC) between the two plugins.
Language bindings will also be an interesting exercise ;)
Yes, the language bindings lag behind what's available because they aren't generated ...
I still need to revive my patches for adding fua support to python bindings... -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org