From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Feng Tang <feng.tang@intel.com>
Cc: marcel@holtmann.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: l2cap: fix a NULL pointer oops in l2cap_conn_start
Date: Sun, 27 Feb 2011 17:13:58 -0300 [thread overview]
Message-ID: <20110227201357.GF2166@joana> (raw)
In-Reply-To: <1298361804-11733-1-git-send-email-feng.tang@intel.com>
Hi Feng,
* Feng Tang <feng.tang@intel.com> [2011-02-22 16:03:24 +0800]:
> When I try to setup a PAND connection between the sever and client,
> the server side always get a NULL pointer oops in l2cap_conn_start()
> right after the client run "pand -r PANU -c sever_addr". Don't have
> the boot log as it's an immediate hang.
>
> Simply adding this "if (parent)" check will fix it, don't know whether
> it fix the real problem. Anyway, send it as a hint.
I pushed a proper fix for this issues, see the bluetooth-2.6 tree.
--
Gustavo F. Padovan
http://profusion.mobi
prev parent reply other threads:[~2011-02-27 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 8:03 [PATCH] Bluetooth: l2cap: fix a NULL pointer oops in l2cap_conn_start Feng Tang
2011-02-27 20:13 ` Gustavo F. Padovan [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=20110227201357.GF2166@joana \
--to=padovan@profusion.mobi \
--cc=feng.tang@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).