linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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-rc7: unpriviledged user crashes kernel using bluetooth
Date: Sat, 31 Aug 2013 12:42:38 +0200	[thread overview]
Message-ID: <20130831104238.GA7767@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130831101451.GC7029@amd.pavel.ucw.cz>

On Sat 2013-08-31 12:14:51, Pavel Machek wrote:
> On Sat 2013-08-31 12:09:33, Pavel Machek wrote:
> > Hi!
> > 
> > > . Python sources for client/server are at 
> > > 
> > > http://tui.cvs.sourceforge.net/viewvc/tui/tui/liveview/
> > > 
> > > . My kernels like to warn about
> > System is debian stable with gnome2.
> 
> And no, it is not fixed in 3.11-rc7.

2.6.32-5-686 from debian seems to work.

Notice that I probably have modemmanager fighting with my own
server, that is experiencing problem described in
http://ubuntuforums.org/showthread.php?t=2056285 . That still should
not allow me to crash the kernel.
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2013-08-31 10:42 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
2013-08-31 10:12   ` 3.10: " Pavel Machek
2013-08-31 10:14   ` 3.11-rc2: " Pavel Machek
2013-08-31 10:42     ` Pavel Machek [this message]
2013-09-01 16:55       ` 3.11-rc7: " 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=20130831104238.GA7767@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).