From: Michael Knudsen <m.knudsen@samsung.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Stop BCSP/H5 timer before cleaning up
Date: Tue, 04 Mar 2014 09:19:21 +0100 [thread overview]
Message-ID: <53158C89.9010200@samsung.com> (raw)
In-Reply-To: <20140304071456.GA30165@localhost.P-661HNU-F1>
On 03/04/2014 08:14 AM, Johan Hedberg wrote:
>>> When stopping BCSP/H5, stop the retransmission timer before proceeding
>>> to clean up packet queues. The previous code had a race condition where
>>> the timer could trigger after the packet lists and protocol structure
>>> had been removed which lead to dereferencing NULL or use-after-free bugs.
>>
>> No interest?
>
> I was just discussing this yesterday with Marcel (that we seem to have
> forgotten about this patch). The only concern is whether it's safe to
> sleep in the *_close callbacks (since you use del_timer_sync). Have you
> verified that this doesn't cause any issues?
Our internal testing was reliably triggering the crash before and
has been stable since our fix went into local trees. I expected
sleeping to be fine since the path is in process context, and I
found that slip uses the same approach:
drivers/net/slip/slip.c:slip_close()
I think I saw other line disciplines that did the same but I don't
recall which ones.
Btw. if this is committed, there is a small typo in the message I
used: Instead of ``lead'' it should be ``led''.
-m.
next prev parent reply other threads:[~2014-03-04 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 8:48 [PATCH] Bluetooth: Stop BCSP/H5 timer before cleaning up Michael Knudsen
2014-03-04 5:25 ` Michael Knudsen
2014-03-04 7:14 ` Johan Hedberg
2014-03-04 8:19 ` Michael Knudsen [this message]
2014-03-04 9:05 ` Johan Hedberg
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=53158C89.9010200@samsung.com \
--to=m.knudsen@samsung.com \
--cc=linux-bluetooth@vger.kernel.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.