From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: peter.maydell@linaro.org, hangaohuai@huawei.com,
qemu-trivial@nongnu.org, Stefan Weil <sw@weilnetz.de>,
Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, peter.huangpeng@huawei.com,
shannon.zhao@linaro.org, Shannon Zhao <zhaoshenglong@huawei.com>
Subject: Re: [Qemu-trivial] [PATCH] hw/bt/sdp: Fix resource leak detect by coverity
Date: Mon, 16 Mar 2015 09:13:40 +0100 [thread overview]
Message-ID: <550690B4.7000506@redhat.com> (raw)
In-Reply-To: <87a8zd4cy7.fsf@blackfin.pond.sub.org>
On 16/03/2015 08:29, Markus Armbruster wrote:
> > Well, in this case the bug in bt_l2cap_sdp_close_ch is much worse than a
> > resource leak. But bluetooth is not the utmost priority in QEMU
> > development...
>
> To put it more bluntly: it's rotting in peace.
>
> Occasional drive-by fixes won't stop the rot, a dedicated maintener
> could.
I disagree. The code is not that good, but apparently it works.
Samsung folks are using it and presented their work at KVM Forum 2014.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: peter.maydell@linaro.org, hangaohuai@huawei.com,
qemu-trivial@nongnu.org, Stefan Weil <sw@weilnetz.de>,
Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, peter.huangpeng@huawei.com,
shannon.zhao@linaro.org, Shannon Zhao <zhaoshenglong@huawei.com>
Subject: Re: [Qemu-devel] [PATCH] hw/bt/sdp: Fix resource leak detect by coverity
Date: Mon, 16 Mar 2015 09:13:40 +0100 [thread overview]
Message-ID: <550690B4.7000506@redhat.com> (raw)
In-Reply-To: <87a8zd4cy7.fsf@blackfin.pond.sub.org>
On 16/03/2015 08:29, Markus Armbruster wrote:
> > Well, in this case the bug in bt_l2cap_sdp_close_ch is much worse than a
> > resource leak. But bluetooth is not the utmost priority in QEMU
> > development...
>
> To put it more bluntly: it's rotting in peace.
>
> Occasional drive-by fixes won't stop the rot, a dedicated maintener
> could.
I disagree. The code is not that good, but apparently it works.
Samsung folks are using it and presented their work at KVM Forum 2014.
Paolo
next prev parent reply other threads:[~2015-03-16 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 9:47 [Qemu-trivial] [PATCH] hw/bt/sdp: Fix resource leak detect by coverity Shannon Zhao
2015-03-14 9:47 ` [Qemu-devel] " Shannon Zhao
2015-03-14 10:07 ` [Qemu-trivial] " Stefan Weil
2015-03-14 10:07 ` Stefan Weil
2015-03-15 9:21 ` [Qemu-trivial] " Paolo Bonzini
2015-03-15 9:21 ` [Qemu-devel] " Paolo Bonzini
2015-03-15 10:23 ` [Qemu-trivial] " Michael Tokarev
2015-03-15 10:23 ` [Qemu-devel] " Michael Tokarev
2015-03-15 14:11 ` [Qemu-trivial] " Paolo Bonzini
2015-03-15 14:11 ` [Qemu-devel] " Paolo Bonzini
2015-03-16 7:29 ` [Qemu-trivial] " Markus Armbruster
2015-03-16 7:29 ` Markus Armbruster
2015-03-16 8:13 ` Paolo Bonzini [this message]
2015-03-16 8:13 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2015-03-14 3:42 [Qemu-trivial] " Shannon Zhao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=550690B4.7000506@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=hangaohuai@huawei.com \
--cc=mjt@tls.msk.ru \
--cc=peter.huangpeng@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=shannon.zhao@linaro.org \
--cc=sw@weilnetz.de \
--cc=zhaoshenglong@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.