On Wed, Jul 04, 2012 at 04:17:39PM +0200, Wido den Hollander wrote:
>
>
> On 04-07-12 14:08, Eric Blake wrote:
> >[adding gnulib]
> >
> >On 07/04/2012 02:45 AM, Daniel P. Berrange wrote:
> >
> ==6825==
> ==6825== Invalid read of size 4
> ==6825==at 0xA57E4B9: base64_encode (in
>
On Wed, Jul 04, 2012 at 06:08:59AM -0600, Eric Blake wrote:
> [adding gnulib]
>
> On 07/04/2012 02:45 AM, Daniel P. Berrange wrote:
>
> >>> ==6825==
> >>> ==6825== Invalid read of size 4
> >>> ==6825==at 0xA57E4B9: base64_encode (in
> >>> /usr/lib/x86_64-linux-gnu/libroken.so.18.1.0)
> >>> =
On 04-07-12 14:08, Eric Blake wrote:
[adding gnulib]
On 07/04/2012 02:45 AM, Daniel P. Berrange wrote:
==6825==
==6825== Invalid read of size 4
==6825==at 0xA57E4B9: base64_encode (in
/usr/lib/x86_64-linux-gnu/libroken.so.18.1.0)
==6825==by 0x10DDBC98: base64_encode_alloc (base64.c:
[adding gnulib]
On 07/04/2012 02:45 AM, Daniel P. Berrange wrote:
>>> ==6825==
>>> ==6825== Invalid read of size 4
>>> ==6825==at 0xA57E4B9: base64_encode (in
>>> /usr/lib/x86_64-linux-gnu/libroken.so.18.1.0)
>>> ==6825==by 0x10DDBC98: base64_encode_alloc (base64.c:140)
>>>
>>> This one
On 04-07-12 10:45, Daniel P. Berrange wrote:
On Wed, Jul 04, 2012 at 10:24:38AM +0200, Wido den Hollander wrote:
On 03-07-12 17:21, Daniel P. Berrange wrote:
On Tue, Jul 03, 2012 at 05:11:48PM +0200, Wido den Hollander wrote:
Yes, there is memory corruption somewhere. I never used valgrind
On Wed, Jul 04, 2012 at 10:24:38AM +0200, Wido den Hollander wrote:
>
>
> On 03-07-12 17:21, Daniel P. Berrange wrote:
> >On Tue, Jul 03, 2012 at 05:11:48PM +0200, Wido den Hollander wrote:
> >>Yes, there is memory corruption somewhere. I never used valgrind
> >>before, but the output seems to sh
On 03-07-12 17:21, Daniel P. Berrange wrote:
On Tue, Jul 03, 2012 at 05:11:48PM +0200, Wido den Hollander wrote:
Yes, there is memory corruption somewhere. I never used valgrind
before, but the output seems to show.
I ran libvirtd inside a screen, I've attached the screenlog with all
the outp
On Tue, Jul 03, 2012 at 05:11:48PM +0200, Wido den Hollander wrote:
> Yes, there is memory corruption somewhere. I never used valgrind
> before, but the output seems to show.
>
> I ran libvirtd inside a screen, I've attached the screenlog with all
> the output.
>
> At the end you'll see there is
On 03-07-12 16:54, Daniel P. Berrange wrote:
On Tue, Jul 03, 2012 at 04:42:54PM +0200, Wido den Hollander wrote:
On 03-07-12 15:13, Daniel P. Berrange wrote:
That is really bizarre. Can you look at what is actually stored
in the .base64 file each time ? And what 'secret-get-value'
replies
On Tue, Jul 03, 2012 at 04:42:54PM +0200, Wido den Hollander wrote:
>
>
> On 03-07-12 15:13, Daniel P. Berrange wrote:
> >>>
> >>>That is really bizarre. Can you look at what is actually stored
> >>>in the .base64 file each time ? And what 'secret-get-value'
> >>>replies with ?
> >>
> >>I haven't
On 03-07-12 15:13, Daniel P. Berrange wrote:
That is really bizarre. Can you look at what is actually stored
in the .base64 file each time ? And what 'secret-get-value'
replies with ?
I haven't been able to look into this any further, however: I just
downloaded 0.9.13 from the libvirt websit
On Tue, Jul 03, 2012 at 03:11:59PM +0200, Wido den Hollander wrote:
>
>
> On 25-06-12 16:54, Daniel P. Berrange wrote:
> >
> >>Notice this behavior:
> >>
> >>root@stack01:~# virsh secret-set-value
> >>322bccea-f2ed-4eae-a7e5-d0793ffb162d
> >>AQAE+uJPCFpELBAAkTniQvHabBGj0Quwnu2imA==
> >>Secret val
On 25-06-12 16:54, Daniel P. Berrange wrote:
Notice this behavior:
root@stack01:~# virsh secret-set-value
322bccea-f2ed-4eae-a7e5-d0793ffb162d
AQAE+uJPCFpELBAAkTniQvHabBGj0Quwnu2imA==
Secret value set
root@stack01:~# md5sum
/etc/libvirt/secrets/322bccea-f2ed-4eae-a7e5-d0793ffb162d.base64
b4
On 06/25/2012 04:54 PM, Daniel P. Berrange wrote:
On Mon, Jun 25, 2012 at 04:37:48PM +0200, Wido den Hollander wrote:
Hi,
On one of my systems I'm having troubles with my RBD storage backend.
At first I thought it was a problem with my code, but after trying
the same code on a second machine I
On Mon, Jun 25, 2012 at 04:37:48PM +0200, Wido den Hollander wrote:
> Hi,
>
> On one of my systems I'm having troubles with my RBD storage backend.
>
> At first I thought it was a problem with my code, but after trying
> the same code on a second machine I'm a bit confused.
>
> The problem is th
Hi,
On one of my systems I'm having troubles with my RBD storage backend.
At first I thought it was a problem with my code, but after trying the
same code on a second machine I'm a bit confused.
The problem is that the storage backend tries to retrieve the value of a
secret and base64 decode
16 matches
Mail list logo