search for: 9cc62b6

...| 7 +++- > server/filters.c | 61 +++++++++++++++++++++++++++++ > server/plugins.c | 72 +++++++++++++++++++++++++++++++++- > 8 files changed, 275 insertions(+), 5 deletions(-) > [...] >diff --git a/docs/nbdkit-plugin.pod b/docs/nbdkit-plugin.pod >index 47545f3..9cc62b6 100644 >--- a/docs/nbdkit-plugin.pod >+++ b/docs/nbdkit-plugin.pod [...] >@@ -717,6 +731,78 @@ If there is an error, C<.zero> should call C<nbdkit_error> with an > error message, and C<nbdkit_set_error> to record an appropriate error > (unless C<errno> is su...

This tentative commit implements extents/can_extents, roughly as discussed in the previous thread here: https://www.redhat.com/archives/libguestfs/2019-March/msg00017.html I can't say that I'm a big fan of having the plugin allocate an extents array. There are no other plugin callbacks currently where we require the plugin to allocate complex data structures (or indeed do any allocation

...ror> with an +error message B<and> return -1 with C<err> set to the positive errno +value to return to the client. + =head1 ERROR HANDLING If there is an error in the filter itself, the filter should call diff --git a/docs/nbdkit-plugin.pod b/docs/nbdkit-plugin.pod index 47545f3..9cc62b6 100644 --- a/docs/nbdkit-plugin.pod +++ b/docs/nbdkit-plugin.pod @@ -555,6 +555,20 @@ This callback is not required. If omitted, then nbdkit always tries C<.zero> first if it is present, and gracefully falls back to C<.pwrite> if C<.zero> was absent or failed with C<EOPNOTSU...