Displaying 4 results from an estimated 4 matches for "xzfile_get_size".
Did you mean:
file_get_size
2019 Jan 30
3
[PATCH nbdkit] xz: Do not pass can_write through to the plugin.
I'm not sure that this fix is really correct.
An alternate way I can think to fix this would be for the core server
to maintain a readonly flag for each layer (instead of just per-
server).
You could also argue that our readonly test in
server/connections.c:compute_eflags is wrong and/or that the
implementations of server/plugins.c:plugin_can_write and
server/filters.c:filter_can_write have
2019 Jan 30
0
[PATCH nbdkit] xz: Do not pass can_write through to the plugin.
...lse.
---
filters/xz/xz.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/filters/xz/xz.c b/filters/xz/xz.c
index 28a6a81..5ff791e 100644
--- a/filters/xz/xz.c
+++ b/filters/xz/xz.c
@@ -173,6 +173,13 @@ xz_get_size (struct nbdkit_next_ops *next_ops, void *nxdata, void *handle)
return xzfile_get_size (h->xz);
}
+static int
+xz_can_write (struct nbdkit_next_ops *next_ops, void *nxdata,
+ void *handle)
+{
+ return 0;
+}
+
/* Read data from the file. */
static int
xz_pread (struct nbdkit_next_ops *next_ops, void *nxdata,
@@ -225,6 +232,7 @@ static struct nbdkit_filter filter...
2018 Nov 21
3
[PATCH nbdkit v2 0/3] Rewrite xz plugin as a filter.
v2:
- Fixes a number of bugs in corner cases.
- Uses a 1M block size to fetch from the underlying plugin. This
improves performance considerably.
I also tested this much more thoroughly and can't find any more bugs.
Rich.
2018 Nov 21
5
[PATCH nbdkit 0/2] Rewrite xz plugin as a filter.
Matt asked if xz should really be a filter rather than a plugin. The
answer is yes, of course it should be! That's been something in the
todo file for a while.
The commit converts the xz plugin code into a filter (leaving the
plugin around, but deprecating it).
plugin: nbdkit xz file.xz
filter: nbdkit --filter=xz file file.xz
plugin: # can't be done
filter: nbdkit