From: Johan Hedberg <johan.hedberg@gmail.com>
To: Paulo Alcantara <paulo.alcantara@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] agent: Fix segmentation fault
Date: Wed, 30 May 2012 10:31:39 +0300 [thread overview]
Message-ID: <20120530073139.GA6539@x220> (raw)
In-Reply-To: <1338330726-11517-1-git-send-email-paulo.alcantara@openbossa.org>
Hi Paulo,
On Tue, May 29, 2012, Paulo Alcantara wrote:
> This patch fixes a segmentation fault when the agent leaves the bus
> and there is a request passkey pending.
>
> bluetoothd[3137]: src/agent.c:agent_exited() Agent exited without
> calling Unregister
> ==3137== Invalid read of size 8
> ==3137== at 0x4489E7: device_get_adapter (device.c:2197)
> ==3137== by 0x448C69: passkey_cb (device.c:2757)
> ==3137== by 0x43FA47: agent_free (agent.c:168)
> ==3137== by 0x40A738: service_filter (watch.c:477)
> ==3137== by 0x40A450: message_filter (watch.c:527)
> ==3137== by 0x516451B: dbus_connection_dispatch (in
> /usr/lib64/libdbus-1.so.3.5.8)
> ==3137== by 0x409387: message_dispatch (mainloop.c:76)
> ==3137== by 0x4E7986A: g_timeout_dispatch (in
> /usr/lib64/libglib-2.0.so.0.3000.2)
> ==3137== by 0x4E78091: g_main_context_dispatch (in
> /usr/lib64/libglib-2.0.so.0.3000.2)
> ==3137== by 0x4E78887: g_main_context_iterate.clone.6 (in
> /usr/lib64/libglib-2.0.so.0.3000.2)
> ==3137== by 0x4E78DD9: g_main_loop_run (in
> /usr/lib64/libglib-2.0.so.0.3000.2)
> ==3137== by 0x431AA6: main (main.c:542)
> ==3137== Address 0xe818247c89102594 is not stack'd, malloc'd or
> (recently) free'd
> ---
> src/agent.c | 5 +++++
> 1 file changed, 5 insertions(+)
Applied. Thanks.
Johan
prev parent reply other threads:[~2012-05-30 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 22:32 [PATCH BlueZ] agent: Fix segmentation fault Paulo Alcantara
2012-05-30 7:31 ` Johan Hedberg [this message]
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=20120530073139.GA6539@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=paulo.alcantara@openbossa.org \
/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.