On Mon, Feb 17, 2020 at 06:03:40AM -0600, Eric Blake wrote:
> On 2/17/20 2:06 AM, Niels de Vos wrote:
> > On Fri, Jan 31, 2020 at 11:44:26AM -0600, Eric Blake wrote:
> > > block.c already defaults to 0 if we don't provide a callback; there's
> > > no need to write a callback that always fails.
> >
On 2/17/20 6:03 AM, Eric Blake wrote:
>
> Creation or truncation should behave just as on a file on a local
> filesystem. So maybe qemu_gluster_known_zeroes is not needed at all?
Which version of gluster first required a regular filesystem backing for
all gluster files? Does qemu support o
On 2/17/20 2:06 AM, Niels de Vos wrote:
On Fri, Jan 31, 2020 at 11:44:26AM -0600, Eric Blake wrote:
block.c already defaults to 0 if we don't provide a callback; there's
no need to write a callback that always fails.
Signed-off-by: Eric Blake
Reviewed-by: Niels de Vos
Per your other mess
On Fri, Jan 31, 2020 at 11:44:26AM -0600, Eric Blake wrote:
> block.c already defaults to 0 if we don't provide a callback; there's
> no need to write a callback that always fails.
>
> Signed-off-by: Eric Blake
Reviewed-by: Niels de Vos
> ---
> block/gluster.c | 14 --
> 1 file ch
On Fri 31 Jan 2020 06:44:26 PM CET, Eric Blake wrote:
> block.c already defaults to 0 if we don't provide a callback; there's
> no need to write a callback that always fails.
>
> Signed-off-by: Eric Blake
Reviewed-by: Alberto Garcia
Berto
31.01.2020 20:44, Eric Blake wrote:
block.c already defaults to 0 if we don't provide a callback; there's
no need to write a callback that always fails.
Signed-off-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
--
Best regards,
Vladimir
block.c already defaults to 0 if we don't provide a callback; there's
no need to write a callback that always fails.
Signed-off-by: Eric Blake
---
block/gluster.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/block/gluster.c b/block/gluster.c
index 4fa4a77a4777..9d952c70981b
