From: Mika Linnanoja <mika.linnanoja@nokia.com>
To: padovan@profusion.mobi
Cc: linux-bluetooth@vger.kernel.org,
ext Ville Tervo <ville.tervo@nokia.com>,
Antti Julku <antti.julku@nokia.com>,
ext Marcel Holtmann <marcel@holtmann.org>,
Lukasz Rymanowski <lukasz.rymanowski@tieto.com>,
linus.walleij@stericsson.com,
par-gunnar.p.hjalmdahl@stericsson.com
Subject: Re: [PATCH] bluetooth: Fix for security block issue.
Date: Fri, 06 May 2011 10:28:23 +0300 [thread overview]
Message-ID: <4DC3A317.9060700@nokia.com> (raw)
In-Reply-To: <4DC390C0.1000607@nokia.com>
On 05/06/2011 09:10 AM, Mika Linnanoja wrote:
> Hi.
>
> Was not happening on ubuntu 9.04 (2.6.28.x) and ubuntu 9.10 (2.6.31.x).
>
> Since 10.04 (2.6.32.x) it has been happening to my knowledge.
>
> It's rather easy to reproduce also manually just by trying to send files in a
> loop via OPP between e.g. 2 ubuntu boxes when both have BT2.1 usb dongles
> (devices can be paired, doesn't help).
One another thing; this specific patch doesn't apply on top of your
linux-bluetooth or bluetooth-next anymore due to the refactoring work (.39 level).
Applying it on top of 2.6.38.x kernel[1] works, but after sending OPP towards
PC running with applied kernel I get kernel oops/crash like:
[ 143.503531] Call Trace:
[ 143.503531] [<c12eaff2>] acpi_idle_enter_simple+0x105/0x13d
[ 143.820013] [<c12eb114>] acpi_idle_enter_bm+0xd5/0x25e
[ 143.820017] [<c142000d>] cpuidle_idle_call+0x7d/0x160
[ 143.820020] [<c10092ca>] cpu_idle+0x8a/0xc0
[ 143.820023] [<c104021e>] ? complete+0x4e/0x60
[ 143.820026] [<c15055cd>] rest_init+0x5d/0x70
[ 143.820029] [<c17a87ee>] start_kernel+0x35f/0x366
[ 143.820032] [<c17a82a3>] ? pass_all_bootoptions+0x0/0x149
[ 143.820036] [<c17a80f1>] i386_start_kernel+0xe0/0xe8
After that trying "hciconfig hci0 -a" results in timeout. That trace doesn't
look like bt specific at all to my untrained eye.
Stock kernel without this patch doesn't cause such kind of issue. Of course it
could be built somehow differently, I'm not an expert, followed some blog's
instructions[2].
BR,
Mika
[1] git cloned git://kernel.ubuntu.com/ubuntu/ubuntu-natty.git
[2] http://parabing.com/2011/04/28/ubuntu-natty-a-custom-kernel-is-what-you-want/
prev parent reply other threads:[~2011-05-06 7:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 14:27 [PATCH] bluetooth: Fix for security block issue Lukasz Rymanowski
2011-01-25 16:13 ` Marcel Holtmann
2011-04-28 9:39 ` Antti Julku
2011-04-28 9:51 ` Ville Tervo
2011-04-29 7:49 ` Mika Linnanoja
2011-05-04 7:53 ` Lukasz.Rymanowski
2011-05-04 15:03 ` Luiz Augusto von Dentz
2011-05-05 19:09 ` Gustavo F. Padovan
2011-09-21 7:22 ` Antti Julku
2011-09-21 8:01 ` Marcel Holtmann
2011-05-05 19:02 ` Gustavo F. Padovan
2011-05-06 6:10 ` Mika Linnanoja
2011-05-06 7:28 ` Mika Linnanoja [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=4DC3A317.9060700@nokia.com \
--to=mika.linnanoja@nokia.com \
--cc=antti.julku@nokia.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lukasz.rymanowski@tieto.com \
--cc=marcel@holtmann.org \
--cc=padovan@profusion.mobi \
--cc=par-gunnar.p.hjalmdahl@stericsson.com \
--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).