From: Marcel Holtmann <marcel@holtmann.org>
To: Yuri Ershov <ext-yuri.ershov@nokia.com>
Cc: davem@davemloft.net, padovan@profusion.mobi,
jprvita@profusion.mobi, linux-bluetooth@vger.kernel.org,
ville.tervo@nokia.com, andrei.emeltchenko@nokia.com
Subject: Re: [PATCH] bluetooth: Fix NULL pointer dereference issue
Date: Fri, 29 Oct 2010 23:43:29 +0200 [thread overview]
Message-ID: <1288388609.3322.40.camel@aeonflux> (raw)
In-Reply-To: <456b20879a6fc3e434463389ef25c4d5cf8803d4.1288262806.git.ext-yuri.ershov@nokia.com>
Hi Yuri,
> This patch fixes NULL pointer dereference at running test with
> connect-transfer-disconnect in loop. The problem conditions are the
> following: there are 2 BT devices. The first one listens and
> receives (l2test -r), the second one makes "connect-disconnect-
> connect..." sequence (l2test -c -b 1000 -i hci0 -P 10 <addr>).
> After some time this will cause the race between functions
> bt_accept_dequeue and l2cap_chan_del. The function l2cap_chan_del
> sets the socket state to BT_CLOSED, unlinks and kills the socket
> in the middle of bt_accept_dequeue, then at running the removed code
> kernel oops appears.
it could be that we have this in here for RFCOMM. Can you retest it with
this with using RFCOMM and see if we get dangling RFCOMM sockets. You
need to test both directions, incoming and outgoing.
Regards
Marcel
next prev parent reply other threads:[~2010-10-29 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 10:52 [PATCH] bluetooth: Fix NULL pointer dereference issue Yuri Ershov
2010-10-29 21:43 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-21 16:08 Yuri Ershov
2010-10-22 13:58 ` Gustavo F. Padovan
2010-10-25 12:23 ` Yuri Ershov
2010-10-28 9:58 ` Gustavo F. Padovan
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=1288388609.3322.40.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=andrei.emeltchenko@nokia.com \
--cc=davem@davemloft.net \
--cc=ext-yuri.ershov@nokia.com \
--cc=jprvita@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
--cc=ville.tervo@nokia.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 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).