From: Pavel Machek <pavel@ucw.cz>
To: marcel@holtmann.org, gustavo@padovan.org,
johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 3.11-rc2: unpriviledged user crashes kernel using bluetooth
Date: Sat, 31 Aug 2013 12:09:33 +0200 [thread overview]
Message-ID: <20130831100933.GA7029@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130831100127.GA6711@amd.pavel.ucw.cz>
Hi!
> . Python sources for client/server are at
>
> http://tui.cvs.sourceforge.net/viewvc/tui/tui/liveview/
>
> . My kernels like to warn about
>
> Aug 31 11:46:37 duo kernel: WARNING: CPU: 1 PID: 1 at
> net/wireless/reg.c:423 regulatory_init+0x92/0xff()
> Aug 31 11:46:37 duo kernel: db.txt is empty, you should update it...
>
> . 3.10 does not seem to be affected.
When I said 3.10 was not affected, I was wrong. 3.10 survived the
test, but when I attempted to reboot the box, I got
WARNING: at lib/list_debug.c:59 __list_del_entry+0xac/0xe0()
list_del_corruption. prev->next should be f44fffd4, but was f44c402c
...
...Comm: bluetoothd....
Call trace:
...
__list_del_entry
cd_forget
evict
iput
System is debian stable with gnome2.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2013-08-31 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 10:01 3.11-rc2: unpriviledged user crashes kernel using bluetooth Pavel Machek
2013-08-31 10:09 ` Pavel Machek [this message]
2013-08-31 10:12 ` 3.10: " Pavel Machek
2013-08-31 10:14 ` 3.11-rc2: " Pavel Machek
2013-08-31 10:42 ` 3.11-rc7: " Pavel Machek
2013-09-01 16:55 ` Gustavo Padovan
2013-09-01 18:50 ` 3.11-final plan: unpriviledged user can crash the kernel (using bluetooth rfcomm) Pavel Machek
2013-09-01 20:16 ` Marcel Holtmann
2013-09-01 22:12 ` Pavel Machek
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=20130831100933.GA7029@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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).