Displaying 3 results from an estimated 3 matches for "_nbdkit_version".
2019 Aug 27
3
[nbdkit PATCH 0/2] RFC: tighter filter versions
This is not intended for v1.14. In fact, we may decide that the
second patch is too gross, although the first one still seems like a
useful improvement in isolation.
I will also point out that all our filters are in-tree, and set the
user-controlled field .version to the current release string. We
could replace the second patch with a simpler one that just checks
._api_version as an int (as
2019 Aug 30
0
[nbdkit PATCH 1/9] server: Fewer dereferences in filter
..."%s: %s: filter is incompatible with this version of nbdkit, "
"and appears to stem from nbdkit 1.14 or earlier\n",
- program_name, f->filename);
+ program_name, filename);
exit (EXIT_FAILURE);
}
if (strcmp (filter->_nbdkit_version, NBDKIT_VERSION_STRING) != 0) {
fprintf (stderr,
"%s: %s: filter is incompatible with this version of nbdkit "
"(_nbdkit_version = %s)\n",
- program_name, f->filename, filter->_nbdkit_version);
+ program_name, filena...
2019 Aug 30
15
[nbdkit PATCH 0/9] can_FOO caching, more filter validation
It's easy to use the sh script to demonstrate that nbdkit is
inefficiently calling into .get_size, .can_fua, and friends more than
necessary. We've also commented on the list in the past that it would
be nice to ensure that when filters call into next_ops, they are not
violating constraints (as we've have to fix several bugs in the past
where we did not have such checking to protect