On Fri, Mar 03, 2017 at 09:35:16AM +0100, Markus Armbruster wrote:
> Niels de Vos writes:
>
> > On Fri, Mar 03, 2017 at 08:38:45AM +0100, Markus Armbruster wrote:
> >> Niels de Vos writes:
> >>
> >> > On Thu, Mar 02, 2017 at 10:44:03PM +0100, Markus Armbruster wrote:
> >> >> To reproduce, run
>
Niels de Vos writes:
> On Fri, Mar 03, 2017 at 08:38:45AM +0100, Markus Armbruster wrote:
>> Niels de Vos writes:
>>
>> > On Thu, Mar 02, 2017 at 10:44:03PM +0100, Markus Armbruster wrote:
>> >> To reproduce, run
>> >>
>> >> $ valgrind qemu-system-x86_64 --nodefaults -S --drive
>> >> driv
On Fri, Mar 03, 2017 at 08:38:45AM +0100, Markus Armbruster wrote:
> Niels de Vos writes:
>
> > On Thu, Mar 02, 2017 at 10:44:03PM +0100, Markus Armbruster wrote:
> >> To reproduce, run
> >>
> >> $ valgrind qemu-system-x86_64 --nodefaults -S --drive
> >> driver=gluster,volume=testvol,path=/
Niels de Vos writes:
> On Thu, Mar 02, 2017 at 10:44:03PM +0100, Markus Armbruster wrote:
>> To reproduce, run
>>
>> $ valgrind qemu-system-x86_64 --nodefaults -S --drive
>> driver=gluster,volume=testvol,path=/a/b/c,server.0.type=xxx
>>
>> Signed-off-by: Markus Armbruster
>> ---
>> block
On Thu, Mar 02, 2017 at 10:44:03PM +0100, Markus Armbruster wrote:
> To reproduce, run
>
> $ valgrind qemu-system-x86_64 --nodefaults -S --drive
> driver=gluster,volume=testvol,path=/a/b/c,server.0.type=xxx
>
> Signed-off-by: Markus Armbruster
> ---
> block/gluster.c | 28 ++---