> > > To: Paul Durrant
> > > > Cc: 'Peter Maydell' ; QEMU Developers > > > de...@nongnu.org>; Anthony Perard
> > > > Subject: Re: [Qemu-devel] QEMU xen coverity issues
> > > >
> > > > Am 15.02.20
> -Original Message-
> From: Kevin Wolf [mailto:kw...@redhat.com]
> Sent: 18 February 2019 10:59
> To: Paul Durrant
> Cc: Anthony Perard ; 'Peter Maydell'
> ; QEMU Developers
> Subject: Re: [Qemu-devel] QEMU xen coverity issues
>
> Am 18.02.2019
; Anthony Perard
> > Subject: Re: [Qemu-devel] QEMU xen coverity issues
> >
> > Am 15.02.2019 um 17:20 hat Paul Durrant geschrieben:
> > > > -Original Message-
> > > [snip]
> > > > >
> > > > > (5) CID 1398649: resou
> -Original Message-
> From: Kevin Wolf [mailto:kw...@redhat.com]
> Sent: 18 February 2019 10:09
> To: Paul Durrant
> Cc: 'Peter Maydell' ; QEMU Developers de...@nongnu.org>; Anthony Perard
> Subject: Re: [Qemu-devel] QEMU xen coverity issues
>
> Am
Am 15.02.2019 um 17:20 hat Paul Durrant geschrieben:
> > -Original Message-
> [snip]
> > >
> > > (5) CID 1398649: resource leak in xen_block_drive_create():
> > >
> > > In hw/block/xen-block.c xen_block_drive_create() Coverity
> > > complains that the call "driver_layer = qdict_new()" alloc
> -Original Message-
[snip]
> >
> > (5) CID 1398649: resource leak in xen_block_drive_create():
> >
> > In hw/block/xen-block.c xen_block_drive_create() Coverity
> > complains that the call "driver_layer = qdict_new()" allocates
> > memory that's leaked because we don't save the pointer any
> -Original Message-
> From: Peter Maydell [mailto:peter.mayd...@linaro.org]
> Sent: 14 February 2019 18:29
> To: QEMU Developers
> Cc: Paul Durrant ; Anthony Perard
>
> Subject: QEMU xen coverity issues
>
> Hi; we've just done another Coverity run, and it's pulled up some
> issues in th
> -Original Message-
> From: Peter Maydell [mailto:peter.mayd...@linaro.org]
> Sent: 14 February 2019 18:29
> To: QEMU Developers
> Cc: Paul Durrant ; Anthony Perard
>
> Subject: QEMU xen coverity issues
>
> Hi; we've just done another Coverity run, and it's pulled up some
> issues in th
Hi; we've just done another Coverity run, and it's pulled up some
issues in the recently changed Xen code. Rather than track them
back to exactly which patches in the recent refactorings resulted
in them, I figured I'd just list them here. Could you take a
look at them, please ?
(1) CID 1398635: x
